Facilitating safer vehicle travel utilizing telematics data

ABSTRACT

Various devices are described, which are configured to use telematics data from one driver to facilitate safer vehicle travel for another driver. A remote server may include (1) a communication unit configured to receive a broadcast including telematics data generated and transmitted from a first mobile device or smart vehicle; and (2) a processor configured to determine (i) a travel event; (ii) a GPS location of the travel event; and/or (iii) an estimated or actual geographical or temporal scope of the travel event from computer analysis of the telematics data. The remote server may transmit a travel event-related wireless communication to a second mobile device or smart vehicle to facilitate safer vehicle travel for a second driver or vehicle based upon the telematics data associated with the first driver/vehicle. Insurance discounts may be provided for individuals or vehicles based upon having or using the risk mitigation or prevention functionality.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority to U.S.patent application Ser. No. 15/860,841, filed on Jan. 3, 2018 andentitled “Facilitating Safer Vehicle Travel Utilizing Telematics Data,”which is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/990,121, filed on Jan. 7, 2016 (now U.S. Pat.No. 9,904,289), which claims the benefit of (1) U.S. Provisional PatentApplication No. 62/105,468, entitled “Broadcasting Telematics Data ToNearby Mobile Computing Devices, Vehicles, And Infrastructure,” filedJan. 20, 2015, (2) U.S. Provisional Patent Application No. 62/113,749,entitled “Broadcasting Telematics Data To Nearby Mobile ComputingDevices, Vehicles, And Infrastructure,” filed Feb. 9, 2015, (3) U.S.Provisional Patent Application No. 62/204,749, entitled “BroadcastingTelematics Data To Nearby Mobile Computing Devices, Vehicles, AndInfrastructure,” filed Aug. 13, 2015, (4) U.S. Provisional PatentApplication No. 62/207,561, entitled “Generating Alert Notifications ByBroadcasting Telematics Data To Nearby Mobile Computing Devices,Vehicles. And Infrastructure,” filed Aug. 20, 2015, (5) U.S. ProvisionalPatent Application No. 62/232,035 entitled “Generating AlertNotifications By Broadcasting Telematics Data To Nearby Mobile ComputingDevices, Vehicles, And Infrastructure,” filed Sep. 24, 2015, (6) U.S.Provisional Patent Application No. 62/232,045, entitled “GeneratingAlert Notifications By Broadcasting Telematics Data To Nearby MobileComputing Devices, Vehicles, And Infrastructure,” filed Sep. 24, 2015,(7) U.S. Provisional Patent Application No. 62/232,050, entitled“Determining Abnormal Traffic Conditions From A Broadcast Of TelematicsData Originating From Another Vehicle,” filed Sep. 24, 2015, (8) U.S.Provisional Patent Application No. 62/232,054, entitled “TakingCorrective Action Based Upon Telematics Data Broadcast From AnotherVehicle,” filed Sep. 24, 2015, (9) U.S. Provisional Patent ApplicationNo. 62/232,065, entitled “Analyzing Telematics Broadcast To DetermineTravel Events And Corrective Actions,” filed Sep. 24, 2015, (10) U.S.Provisional Patent Application No. 62/232,075, entitled “ProvidingInsurance Discounts Based Upon Usage Of Telematics Data-Based RiskMitigation And Prevention Functionality,” filed Sep. 24, 2015, (11) U.S.Provisional Patent Application No. 62/232,083, entitled “DeterminingCorrective Actions Based Upon Broadcast Of Telematics Data OriginatingFrom Another Vehicle,” filed Sep. 24, 2015, (12) U.S. Provisional PatentApplication No. 62/232,090, entitled “Determining Corrective ActionsBased Upon Telematics Data Broadcast From Another Vehicle,” filed Sep.24, 2015, (13) U.S. Provisional Patent Application No. 62/232,097,entitled “Generating Alert Notifications By Broadcasting TrainTelematics Data To Nearby Mobile Computing Devices, Vehicles, AndInfrastructure,” filed Sep. 24, 2015, (14) U.S. Provisional PatentApplication No. 62/247,334, entitled “Generating Alert Notifications ByBroadcasting Train Telematics Data To Nearby Mobile Computing Devices,Vehicles, And Infrastructure,” filed Oct. 28, 2015, and (15) U.S.Provisional Patent Application No. 62/250,286, entitled “GeneratingAlert Notifications By Broadcasting Train Telematics Data To NearbyMobile Computing Devices, Vehicles, And Infrastructure,” filed Nov. 3,2015, the disclosure of each of which is hereby expressly incorporatedby reference herein in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to generating alertnotifications and, more particularly, to generating alert notificationsbased upon an analysis of collected telematics data, which may be usedby other drivers BACKGROUND

Conventional telematics devices may collect certain types of dataregarding vehicle operation. However, conventional telematics devicesand data gathering techniques may have several drawbacks.

BRIEF SUMMARY

In one aspect, telematics data and/or geographic location data may becollected, monitored, measured, and/or generated by one or morecomputing devices associated with a vehicle. The telematics data mayinclude various metrics that indicate the direction, speed, and/ormotion of the vehicle in which the data is associated. The geographiclocation data may include a geographic location of the vehicle, such aslatitude and longitude coordinates, for example. The one or morecomputing devices may include a mobile computing device positionedwithin the vehicle, an on-board computer integrated within the vehicle,and/or a combination of these devices working in conjunction with oneanother. The one or more computing devices may broadcast the telematicsdata and/or the geographic location data to one or more other devices.

The telematics data and/or the geographic location data may be receivedand/or processed by one or more other computing devices to determinewhether an anomalous condition exists, such as a traffic accident, forexample. These one or more other computing devices may be externalcomputing devices (e.g., a remote server), another mobile computingdevice, a smart traffic infrastructure device (e.g., a smart trafficlight), etc. If an anomalous condition is detected, the geographiclocation of the vehicle associated with the telematics data may be usedas a condition to decide whether to generate an alert at (or send analert notification to) the one or more other computing devicesassociated with nearby vehicles.

In one aspect, a computer server (or smart infrastructure) configured touse telematics data associated with a first driver to facilitate safervehicle travel for a second driver may be provided. The computer servermay include (1) a communication unit configured to receive telematicsdata via wireless communication and/or data transmission, the telematicsdata being generated and transmitted from a first mobile device and/orfirst smart vehicle associated with a first driver, (2) a memory unitconfigured to store vehicle navigation information, virtual road maps,and/or computer-readable instructions; and (3) a processor configured toaccess the memory unit and to automatically identify or determine: (i) atravel or traffic event associated with the first mobile device and/orfirst vehicle, (ii) a Global Positioning System (GPS) location or otherlocation of the travel event, and (iii) an estimated or actualgeographical or temporal scope of the travel event from computeranalysis of the telematics data, the processor further being configuredto generate a travel event-related data transmission or wirelesscommunication associated with or detailing the travel event, or locationor extent thereof. The communication unit may be further configured totransmit the travel event-related data transmission or wirelesscommunication to a second mobile device or second vehicle associatedwith the second driver to facilitate the second mobile device or secondvehicle taking corrective action to enable safer vehicle travel for thesecond driver based upon the telematics data associated with the firstdriver. The remote server may include additional, less, or alternatefunctionality, including that discussed elsewhere herein.

In another aspect, a smart infrastructure component configured to usetelematics data from a first driver to facilitate safer vehicle travelfor a second driver may be provided. The smart infrastructure componentmay include (1) a communication unit configured to receive a datatransmission or wireless communication containing or includingtelematics data, the telematics data being generated and transmittedfrom a first mobile device or a first vehicle associated with the firstdriver; (2) a memory unit configured to store vehicle navigationinformation, virtual road maps, and computer-readable instructions; and(3) a processor configured to access the memory unit to automaticallyidentify or determine: (i) a travel event; (ii) a Global PositioningSystem (GPS) location or other location of the travel event; and (iii)an estimated or actual geographical or temporal scope of the travelevent from computer analysis of the telematics data, the processorfurther being configured to generate a travel event-related datatransmission or wireless communication associated with or detailing thetravel event, or location or extent thereof. The communication unit maybe further configured to transmit the travel event-related datatransmission or wireless communication to a second mobile device and/orsecond vehicle associated with the second driver to facilitate thesecond mobile device or second vehicle taking corrective action toenable safer vehicle travel for the second driver based upon thetelematics data associated with the first driver. The smartinfrastructure component may be configured with additional less, oralternate functionality, including that discussed elsewhere herein.

In yet another aspect, an intermediate mobile device or smart vehicleconfigured to use telematics and/or other data from a first driver tofacilitate safer vehicle travel for a second driver, the intermediatemobile device or smart vehicle may be provided. The intermediate mobiledevice or smart vehicle may include (1) a communication unit configuredto receive a data transmission or wireless communication containing orincluding telematics data, the telematics data being generated andtransmitted from a first mobile device or first smart vehicle associatedwith the first driver; (2) a memory unit configured to store vehiclenavigation information, virtual road maps, and/or computer-readableinstructions; (3) a processor configured to access the memory unit toautomatically identify or determine: (i) a travel event; (ii) a GlobalPositioning System (GPS) location or other location of the travel event;and (iii) an estimated or actual geographical or temporal scope of thetravel event from computer analysis of the telematics data, theprocessor further being configured to generate a travel event-relateddata transmission or wireless communication associated with or detailingthe travel event, or location or extent thereof. The communication unitmay be further configured to transmit the travel event-related datatransmission or wireless communication to a second or destination mobiledevice and/or a second smart vehicle associated with the second drivervia peer-to-peer (P2P) communication to facilitate the second mobiledevice or second smart vehicle taking corrective action to enable safervehicle travel for the second driver based upon the telematics dataassociated with the first driver. The intermediate mobile device orsmart vehicle may be configured with additional, less, or alternatefunctionality, including that discussed elsewhere herein.

Advantages will become more apparent to those skilled in the art fromthe following description of the preferred embodiments which have beenshown and described by way of illustration. As will be realized, thepresent embodiments may be capable of other and different embodiments,and their details are capable of modification in various respects.Accordingly, the drawings and description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the system andmethods disclosed therein. It should be understood that each Figuredepicts an embodiment of a particular aspect of the disclosed system andmethods, and that each of the Figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingFigures, in which features depicted in multiple Figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and instrumentalities shown,wherein:

FIG. 1 illustrates a block diagram of an exemplary telematics collectionsystem 100 in accordance with an exemplary aspect of the presentdisclosure;

FIG. 2 illustrates a block diagram of an exemplary alert notificationsystem 200 in accordance with an exemplary aspect of the presentdisclosure;

FIG. 3 illustrates a block diagram of an exemplary computing device ormobile device 300 in accordance with an exemplary aspect of the presentdisclosure;

FIG. 4A illustrates an exemplary mobile computing device home screen 400in accordance with an exemplary aspect of the present disclosure;

FIG. 4B illustrates an exemplary mobile computing device applicationscreen 450 in accordance with an exemplary aspect of the presentdisclosure;

FIG. 5 illustrates a block diagram of an exemplary smart vehicle controlsystem 500 in accordance with an exemplary aspect of the presentdisclosure;

FIG. 6 illustrates a block diagram of an exemplary remote server 600 inaccordance with an exemplary aspect of the present disclosure;

FIG. 7 illustrates a block diagram of an exemplary smart infrastructurecomponent 700 in accordance with an exemplary aspect of the presentdisclosure; and

FIG. 8 illustrates an exemplary computer-implemented method 800 forreceiving, analyzing, and/or broadcasting telematics and/or other dataat or from an intermediary computing device to facilitate safer driving.

The Figures depict preferred embodiments for purposes of illustrationonly. Alternative embodiments of the systems and methods illustratedherein may be employed without departing from the principles of theinvention described herein.

DETAILED DESCRIPTION

The present embodiments relate to, inter alia, determining whether ananomalous condition is detected at the location of a vehicle using oneor more computing devices within or otherwise associated with thevehicle. If the detected anomalous condition may impact or affectanother vehicle on the road, embodiments are described to generateand/or send alert notifications to other vehicles that may be soaffected. As further described throughout the disclosure, the process ofdetecting anomalous conditions and whether they apply to other vehiclesmay be performed through an analysis geographic location data and/ortelematics data broadcasted from one or more computing devices within orotherwise associated with one or more respective vehicles.

The present embodiments may relate to collecting transmitting, and/orreceiving telematics data, and may include a mobile device, avehicle-mounted processor, computer server, web pages, applications,software modules, user interfaces, interactive display screens, memoryunits, and/or other electronic, electrical, and/or wirelesscommunication equipment configured to provide the functionalitydiscussed herein. As compared with the prior art, the presentembodiments include specifically configured computing equipment thatprovide for an enhanced method of collecting telematics and/or othervehicle/driving conditions related data, and performing certain actionsbased upon the data collected. Using the telematics and/or other datacollected, in conjunction with the novel techniques discussed herein,recommendations and/or travel/driving guidance may be provided to remotevehicles and/or drivers.

The present embodiments may solve one or more technical problems relatedto (1) vehicle safety, and/or (2) vehicle navigation by using solutionsor improvements in another technological field, namely telematics.Vehicle safety and vehicle navigation is often impacted by short-termtraffic events that occur with little or no warning. For instance,vehicle accidents may be caused by road construction, other vehicleaccidents, traffic being temporarily re-routed, unexpected bad weather,other drivers or vehicles, etc.

To address these and other problems, telematics data (and/or driverbehavior or vehicle information) may be captured in real-time, or nearreal-time, by a mobile device of a vehicle driver (or passenger). Themobile device may be specifically configured for gathering collecting,and/or generating telematics and/or other data as a vehicle istraveling.

For instance, the mobile device may be equipped with (i) various sensorsand/or meters capable of generating telematics data (GPS unit, speedsensor, speedometer, odometer, gyroscope, compass, accelerometer, etc.)and/or (ii) an application, such as a Telematics Data Application orTelematics “App,” that includes computer instructions and/or softwaremodules stored in a non-transitory memory unit that control collectingand generating telematics and/or other data. The mobile device and/orthe application (or Telematics App) may provide a software module, userinterface, and/or interactive display screen configured to facilitatethe data collection. The mobile device and/or Telematics App executingthereon may be configured to prepare or otherwise format the telematicsand/or other data collected or generated for transmission (via wirelesscommunication and/or data transmission) to a mobile device of a seconddriver, a remote server, another (smart) vehicle, and/or smartinfrastructure—all of which may be equipped with its own Telematics Appor other telematics related applications. The Telematics App may includeother functionality, including the mobile device functionality discussedelsewhere herein.

Alternatively, the mobile device may remotely access a web page, such asvia wireless communication with a remote server. The web page mayprovide the mobile device with the functionality to collect thetelematics and/or other data as the vehicle is moving Additionally oralternatively, the web page may allow the mobile device to upload ortransmit data in real-time, or near real-time, to a mobile device of asecond driver, a remote server, smart infrastructure, and/or another(smart) vehicle.

Additionally or alternatively, a smart vehicle controller or processormay be configured with the same functionality as that of the mobiledevice described above. For instance, a smart vehicle controller mayinclude an application, software module, or computer instructions thatprovide for the telematics and/or other data collection and generationfunctionality discussed herein. The smart vehicle controller may be inwired or wireless communication with various (“smart” or “dumb”)vehicle-mounted meters, sensors, and/or detectors, such as speedometers,speed sensors, compasses, gyros, accelerometers, etc. that collectand/or generate telematics data and/or other data detailing orassociated with vehicle operation, and/or driving or driver behavior.

In one aspect, by solving problems with collecting telematics dataand/or other data associated with driver behavior and/or vehicleoperation or performance, problems with vehicle navigation and/orvehicle operation may be resolved. For instance, telematics dataassociated with a first vehicle may be collected in real-time by amobile device of a first driver. The mobile device may be specificallyconfigured to gather or generate telematics and/or other driver/vehicledata in real-time as the vehicle is traveling, such as via a TelematicsApp running on the mobile device. If a traffic event is encountered,about to be encountered, and/or expected or anticipated to beencountered by the vehicle as it travels (e.g., road construction; heavytraffic; congestion; bad weather conditions; unlawful, unexpected orerratic operation of other vehicles; questionable or abnormal drivingbehavior of other drivers; irresponsible or overly aggressive drivers;un-attentive or tired drivers, etc.), the telematics (and/or data) datacollected may indicate such.

The mobile device itself (and/or Telematics App) may be configured toidentify the type of traffic event and transmit the type of trafficevent to other mobile devices, a remote server, smart vehicles, and/orsmart infrastructure. In one embodiment, the mobile device (and/orTelematics App) may be in wireless communication with a smart vehiclecontrol system of the vehicle, and the smart vehicle control system maytransmit the telematics and/or other data, and/or any associatedwarnings, to a remote server, and/or roadside smart infrastructure ornearby mobile device or vehicles of other drivers (such as to conservebattery power of the mobile device).

Alternatively, the mobile device (and/or Telematics App) may transmitthe telematics and/or other data collected via wireless communicationand/or data transmission to a second computing device—such as a secondmobile device (or another driver), a second and smart vehicle, a remoteserver, and/or road side infrastructure (smart street signs or roadposts, smart toll booths, etc.). After which, the second and remotecomputing device may analyze the telematics and/or other data that iscollected in real-time, or near real-time, to determine traffic eventsin real-time, or near real-time, respectively. Based upon the type andextent of traffic event detected, the second computing device may issuewarnings, determine recommendations, and/or re-route vehicles. Forinstance, the second computing device may cause a display screen or userinterface of a mobile device or smart vehicle controller of remotedrivers to display a map with (1) a current route that the vehicle ison, (2) a virtual representation of the traffic event, and/or (3) analternate or recommended new route to an original destination thatavoids the traffic event.

In one embodiment, a telematics application or software module (e.g.,the Telematics App as discussed herein) may be designed to communicatewith smart vehicles and smart infrastructure. An advantage of this isthat for a vehicle owner that does not have a “smart” vehicle withwireless communication technology, the application and/or softwaremodule deployed on a smart phone or other mobile device may communicatewith smart vehicles and infrastructure (and/or remote servers and othermobile devices). The telematics application and/or software module maybe programmed to provide voice alerts: such as on a two lane road “donot pass-a vehicle is approaching” or “high speed vehicle is approachingto your left (or right);” “traffic light will turn in 10 seconds;” “turnleft to find an open parking space;” “traffic is stopped 1.5 milesahead;” “traffic has slowed to 20 mph 1.5 miles (or 2 blocks) ahead;”“recommended speed for turn ahead is 30 mph;” and/or “ice on bridge (orramp) ahead.”

As an example, a first mobile device may be traveling in a vehicle. Thefirst mobile device may collect telematics data and/or other data, suchas via a telematics application running on one or more processorsmounted within the first mobile device. The first mobile device (and/orthe telematics application) may detect a travel event from the datacollected. For instance, the first mobile device (and/or the telematicsapplication executing thereon) may determine that the vehicle is locatedon the highway, but the vehicle is moving slower than the posted speedlimit. The first mobile device (and/or the telematics application) maythen transmit the data collected and/or an associated message viawireless communication or data transmission to smart roadsideinfrastructure and/or nearby vehicles (or a second mobile devicetraveling within a nearby and second vehicle). The second mobile device(and/or a telematics application running thereon) may then, using thedata received and/or message received from the first mobile device,generate an audible or visual warning or alert of the travel event, suchas “Warning, congestion ahead,” and/or “Recommend taking Exit 10 andtraveling on Highway 12 for 5 miles until Exit 11 to avoid thecongestion ahead.” The second mobile device (and/or associatedtelematics application) may also be able to compare locations of thetravel event with the current location of the second vehicle todetermine if the travel event poses a potential obstacle to the secondvehicle reaching its destination without interruption. Thus, thetelematics data collected using a first mobile device (and/or atelematics application) and associated with a first driver may be usedto alert a second driver (associated with the second mobile device) of atravel event and/or re-route the second vehicle to facilitate safervehicle travel for the second driver and vehicle.

In one aspect, a mobile device (and/or the telematics application) maycompare a vehicle's traveling speed with a known posted speed limit. Ifthe vehicle's speed is below or above the posted speed by a certainthreshold, for example, 10 or 20 miles-per-hour, then the mobile devicemay generate a warning and transmit the warning to roadsideinfrastructure and/or nearby mobile devices or vehicles. For example,the message may state “Slow moving vehicle in right hand lane ahead,”“High speed vehicle approaching from rear;” And/or “High speed vehicleapproaching from ahead.”

Other messages or alerts that may be generated from mobile devices(and/or telematics applications executing thereon), smart vehiclecontrollers, remote servers, and/or smart infrastructure and transmittedto a mobile device of a driver (and/or smart vehicle) may include“Construction 1 mile ahead;” “Rain (or Snow) 5 miles ahead;” “Detour 2blocks ahead;” “Traffic light directly ahead will change from Green toRed starting in 5 seconds;” “Stranded vehicle on right side of road halfa mile ahead;” “Recommend turning right at next intersection to avoidtravel event 3 blocks ahead;” and/or other travel or trafficevent-related messages.

An insurance provider may collect an insured's usage of the vehiclesafety functionality provided herein, such as at an insurance providerremote server and/or via a mobile device application. Based upon anindividual's usage and/or taking travel recommendations, such as travelrecommendations that reduce or lower risk and/or enhance driver orvehicle safety, insurance policies (such as vehicle or life insurancepolicies) may be adjusted, generated, and/or updated. The insuranceprovider remote server may calculate, update, and/or adjust insurancepremiums, rates, discounts, points, programs, etc., such as adjusting aninsurance discount or premium based upon the insured having thefunctionality discussed herein and/or the amount that the insured usesthe functionality discussed herein. The updated insurance policies(and/or premiums, rates, discounts, etc.) may be communicated toinsurance customers for their review, modification, and/or approval—suchas via wireless communication or data transmission from a remote serverto a mobile device or the insured.

Telematics and Vehicle Navigation

In one aspect, by solving problems with collecting telematics dataand/or other data associated with driver behavior and/or vehicleoperation or performance, problems with vehicle navigation and/orvehicle operation may be resolved. For instance, telematics dataassociated with a first vehicle may be collected in real-time by amobile device of a first driver. The mobile device may be specificallyconfigured to gather or generate telematics and/or other driver/vehicledata in real-time as the vehicle is traveling. If a traffic event isencountered, about to be encountered, and/or expected or anticipated tobe encountered by the vehicle as it travels (e.g., road construction;heavy traffic; congestion; bad weather conditions; unlawful, unexpectedor erratic operation of other vehicles; questionable or abnormal drivingbehavior of other drivers; irresponsible or overly aggressive drivers,un-attentive or tired drivers, etc.), the telematics (and/or data) datacollected may indicate such.

The mobile device itself may be configured to identify the type oftraffic event and transmit the type of traffic event to other mobiledevices, a remote server, smart vehicles, and/or smart infrastructure.In one embodiment, the mobile device may be in wireless communicationwith a smart vehicle control system of the vehicle, and the smartvehicle control system may transmit the telematics and/or other data,and/or any associated warnings, to a remote server, and/or roadsidesmart infrastructure or nearby mobile device or vehicles of otherdrivers (such as to conserve battery power of the mobile device).

Additionally or alternatively, the mobile device may transmit thetelematics and/or other data collected via wireless communication and/ordata transmission to a second computing device—such as a second mobiledevice (or another driver), a second and smart vehicle, a remote server,and/or road side infrastructure (smart street signs or road posts, smarttoll booths, etc.). After which, the second and remote computing devicemay analyze the telematics and/or other data that is collected inreal-time, or near real-time, to determine traffic events in real-time,or near real-time, respectively. Based upon the type and extent oftraffic event detected, the second computing device may issue warnings,determine recommendations, and/or re-route vehicles. For instance, thesecond computing device may cause a display screen or user interface ofa mobile device or smart vehicle controller of remote drivers to displaya map with (1) a current route that the vehicle is on, (2) a virtualrepresentation of the traffic event, and/or (3) an alternate orrecommended new route to an original destination that avoids the trafficevent.

Exemplary Telematics Collection System

FIG. 1 illustrates a block diagram of an exemplary telematics collectionsystem 100 in accordance with an exemplary aspect of the presentdisclosure. In some aspects, telematics collection system 100 mayinclude hardware and software applications configured to measure,calculate, generate, and/or collect geographic location data and/ortelematics data indicative of the speed, direction, and/or motion ofvehicle 108. Additionally or alternatively, telematics collection system100 may include hardware and software applications configured to receiveand process geographic location data and/or telematics data sent fromanother telematics collection system, to determine whether an anomalouscondition has been detected, whether to generate an alert, and/orwhether to send an alert notification or other telematics-rated message.Telematics collection system 100 may include various data communicationchannels for facilitating data communications between the varioushardware and software components and/or communications with one or moreexternal components.

Various references are made to “telematics data” throughout thisdisclosure. As discussed herein, the telematics data may include anysuitable type of information that may be used to identify variousanomalous conditions, events, inconveniences, hazards, etc. Examples oftelematics data provided herein may include, but is not limited to, dataincluding sensor metrics or other information (e.g., image and/or videodata) generated, collected, measured, and/or transmitted from anoriginating device, which may be indicative of various physicalproperties, conditions, the environment, and/or other informationassociated with the originating device.

For example, the telematics data may indicate acceleration,deceleration, Global Positioning System (GPS) location, time, braking,data indicative of an originating vehicle turning, the heading and/orspeed of the originating vehicle (e.g., GPS-determined speed, onboardvehicle sensor based speed, etc.) GPS latitude and longitude, a batterylevel of an originating mobile device located in the originatingvehicle, telephone usage information associated with the originatingdevice, angular velocity metrics and/or gyroscope data, current roadlane information associated with the originating vehicle, etc.

To accomplish this, telematics collection system 100 may include anysuitable number of computing devices, such as mobile computing device110 and/or on-board computing device 114, for example. These computingdevices may be disposed within vehicle 108, permanently installed invehicle 108, or removably installed in vehicle 108.

In the present aspects, mobile computing device 110 may be implementedas any suitable computing or mobile device, such as a mobile device(e.g., smartphone, tablet, laptop, wearable electronics, phablet, pager,personal digital assistant (PDA), smart glasses, smart watch orbracelet, etc.), while on-board computer may implemented as ageneral-use on-board computer or processor(s) installed by themanufacturer of vehicle 108 or as an aftermarket modification to vehicle108, for example. In various aspects, mobile computing device 110 and/oron-board computer 114 may be a thin-client device configured tooutsource any suitable portion of processing via communications with oneor more external components.

On-board computer 114 may supplement one or more functions performed bymobile computing device 110 described herein by, for example, sendinginformation to and/or receiving information from mobile computing device110. Mobile computing device 110 and/or on-board computer 114 maycommunicate with one or more external components via links 112 and 118,respectively. Additionally, mobile computing device 110 and on-boardcomputer 114 may communicate with one another directly via link 116.

In one aspect, mobile computing device 110 may be configured withsuitable hardware and/or software (e.g., one or more applications,programs, files, etc.) to determine a geographic location of mobilecomputing device 110 and, hence, vehicle 108, in which it is positioned.Additionally or alternatively, mobile computing device 110 may beconfigured with suitable hardware and/or software to monitor, measure,generate, and/or collect one or more sensor metrics as part of thetelematics data. Mobile computing device 110 may be configured tobroadcast the geographic location data and/or the one or more sensormetrics to one or more external components.

In some aspects, the external components may include another mobilecomputing device substantially similar to or identical to mobilecomputing device 110. In accordance with such aspects, mobile computingdevice 110 may additionally or alternatively be configured to receivegeographic location data and/or sensor metrics broadcasted from anothermobile computing device, the details of which are further discussedbelow. Mobile computing device 110 may be configured to determine, uponreceiving the geographic location data and/or sensor metrics, whether ananomalous condition exists at the geographic location indicated by thegeographic location data. If so, mobile computing device 110 may beconfigured to generate one or more audio and/or video alerts indicativeof the determined anomalous condition.

On-board computer 114 may be configured to perform one or more functionsotherwise performed by mobile computing device 110. However, on-boardcomputer 114 may additionally be configured to obtain geographiclocation data and/or telematics data by communicating with one or morevehicle sensors that are integrated into vehicle 108. For example,on-board computer 114 may obtain geographic location data viacommunication with a vehicle-integrated global navigation satellitesystem (GNSS). To provide additional examples, on-board computer 114 mayobtain one or more metrics related to the speed, direction, and/ormotion of vehicle 108 via any number of suitable sensors, such asspeedometer sensors, braking sensors, airbag deployment sensors, crashdetection sensors, etc.

In one aspect, mobile computing device 110 and/or on-board computer 114may operate independently of one another to generate geographic locationdata and/or telematics data, to receive geographic location data and/ortelematics data broadcasted from another telematics collection system,to determine whether to generate one or more alerts, and/or to generateone or more alert notifications. In accordance with such aspects,telematics collection system 100 may include mobile computing device 110but not on-board computer 114, and vice-versa.

In other aspects, mobile computing device 110 and/or on-board computer114 may operate in conjunction with one another to generate geographiclocation data and/or telematics data, to receive geographic locationdata and/or telematics data broadcasted from another telematicscollection system, to determine whether to generate one or more alerts,and to generate one or more alert notifications. In accordance with suchaspects, telematics collection system 100 may include both mobilecomputing device 110 and on-board computer 114. Mobile computing device110 and on-board computer 114 may share any suitable portion ofprocessing between one another to facilitate the functionality describedherein.

Upon receiving notification alerts from another telematics collectionsystem, aspects include telematics collection system 100 generatingalerts via any suitable audio, video, and/or tactile techniques. Forexample, alerts may be generated via a display implemented by mobilecomputing device 110 and/or on-board computer 114. To provide anotherexample, a tactile alert system 120 (e.g., a seat that can vibrate) maybe configured to generate tactile alerts to a vehicle operator 106 whencommanded by mobile computing device 110 and/or on-board computer 114.To provide another example, audible alerts may be generated via aspeaker 122, which may be part of vehicle 108's integrated speakersystem, for example.

Although telematics collection system 100 is shown in FIG. 1 asincluding one mobile computing device 110 and one on-board computer 114,various aspects include telematics collection system 100 implementingany suitable number of mobile computing devices 110 and/or on-boardcomputers 114.

Exemplary Telematics Alert Notification System

FIG. 2 illustrates a block diagram of an exemplary alert notificationsystem 200 in accordance with an exemplary aspect of the presentdisclosure. In one aspect, alert notification system 200 may include anetwork 201, N number of vehicles 202.1-202.N and respective mobilecomputing devices 204.1-204.N, an external computing device 206, and/oran infrastructure component 208. In one aspect, mobile computing devices204 may be an implementation of mobile computing device 110, as shown inFIG. 1, while vehicles 202 may be an implementation of vehicle 108, alsoshown in FIG. 1. Each of vehicles 202.1 and 202.2 may have an associatedon-board computer, which is not shown in FIG. 2 for purposes of brevity,but may be an implementation of on-board computer 114, as shown inFIG. 1. Each of vehicles 202.1 and 202.2 may be configured for wirelessinter-vehicle communication, such as vehicle-to-vehicle (V2V) wirelesscommunication and/or data transmission.

Although alert notification system 200 is shown in FIG. 2 as includingone network 201, two mobile computing devices 204.1 and 204.2, twovehicles 202.1 and 202.2, one external computing device 206, and/or oneinfrastructure component 208, various aspects include alert notificationsystem 200 implementing any suitable number of networks 201, mobilecomputing devices 204, vehicles 202, external computing devices 206,and/or infrastructure components 208. For example, alert notificationsystem 200 may include a plurality of external computing devices 206 andmore than two mobile computing devices 204, any suitable number of whichbeing interconnected directly to one another and/or via network 201.

In one aspect, each of mobile computing devices 204.1 and 204.2 may beconfigured to communicate with one another directly via peer-to-peer(P2P) wireless communication and/or data transfer. In other aspects,each of mobile computing devices 204.1 and 204.2 may be configured tocommunicate indirectly with one another and/or any suitable device viacommunications over network 201, such as external computing device 206and/or infrastructure component 208, for example. In still otheraspects, each of mobile computing devices 204.1 and 204.2 may beconfigured to communicate directly and indirectly with one and/or anysuitable device, which may be concurrent communications orcommunications occurring at separate times.

Each of mobile computing devices 204.1 and 204.2 may be configured tosend data to and/or receive data from one another and/or via network 201using one or more suitable communication protocols, which may be thesame communication protocols or different communication protocols as oneanother. To provide an example, mobile computing devices 204.1 and 204.2may be configured to communicate with one another via a direct radiolink 203 a, which may utilize, for example, a Wi-Fi direct protocol, anad-hoc cellular communication protocol, etc. Furthermore, mobilecomputing devices 204.1 and 204.2 may be configured to communicate withthe vehicle on-board computers located in vehicles 202.1 and 202.1,respectively, utilizing a BLUETOOTH communication protocol (radio linknot shown).

To provide additional examples, mobile computing devices 204.1 and 204.2may be configured to communicate with one another via radio links 203 band 203 c by each communicating with network 201 utilizing a cellularcommunication protocol. As an additional example, mobile computingdevices 204.1 and/or 204.2 may be configured to communicate withexternal computing device 206 via radio links 203 b, 203 c, and/or 203e. Still further, one or more of mobile computing devices 204.1 and/or204.2 may also be configured to communicate with one or more smartinfrastructure components 208 directly (e.g., via radio link 203 d)and/or indirectly (e.g., via radio links 203 c and 203 f via network201) using any suitable communication protocols.

Mobile computing devices 204.1 and 204.2 may be configured to executeone or more algorithms, programs, applications, etc., to determine ageographic location of each respective mobile computing device (and thustheir associated vehicle) to generate, measure, monitor, and/or collectone or more sensor metrics as telematics data, to broadcast thegeographic data and/or telematics data via their respective radio links,to receive the geographic data and/or telematics data via theirrespective radio links, to determine whether an alert should begenerated based upon the telematics data and/or the geographic locationdata, to generate the one or more alerts, and/or to broadcast one ormore alert notifications.

Network 201 may be implemented as any suitable network configured tofacilitate communications between mobile computing devices 204.1 and/or204.2 and one or more of external computing device 206 and/orinfrastructure component 208. For example, network 201 may include oneor more telecommunication networks, nodes, and/or links used tofacilitate data exchanges between one or more devices, and mayfacilitate a connection to the Internet for devices configured tocommunicate with network 201. Network 201 may include any suitablenumber of interconnected network components that form an aggregatenetwork system, such as dedicated access lines, plain ordinary telephonelines, satellite links, cellular base stations, a public switchedtelephone network (PSTN), etc., or any suitable combination thereof.Network 201 may include, for example, a proprietary network, a securepublic internet, a mobile-based network, a virtual private network, etc.

In aspects in which network 201 facilitates a connection to theInternet, data communications may take place over the network 201 viaone or more suitable Internet communication protocols. For example,network 201 may be implemented as a wireless telephony network (e.g.,GSM, CDMA, LTE, etc.), a Wi-Fi network (e.g., via one or more IEEE802.11 Standards), a WiMAX network, a Bluetooth network, etc. Thus,links 203 a-203 f may represent wired links, wireless links, or anysuitable combination thereof.

In aspects in which mobile computing devices 204.1 and 204.2 communicatedirectly with one another in a peer-to-peer fashion, network 201 may bebypassed and thus communications between mobile computing devices 204.1and 204.2 and external computing device 206 may be unnecessary. Forexample, in some aspects, mobile computing device 204.1 may broadcastgeographic location data and/or telematics data directly to mobilecomputing device 204.2. In this case, mobile computing device 204.2 mayoperate independently of network 201 to determine whether an alertshould be generated at mobile computing device 204.2 based upon thegeographic location data and the telematics data. In accordance withsuch aspects, network 201 and external computing device 206 may beomitted.

However, in other aspects, one or more of mobile computing devices 204.1and/or 204.2 may work in conjunction with external computing device 206to generate alerts. For example, in some aspects, mobile computingdevice 204.1 may broadcast geographic location data and/or telematicsdata, which is received by external computing device 206. In this case,external computing device 206 may be configured to determine whether analert should be sent to mobile computing device 204.2 based upon thegeographic location data and the telematics data.

External computing device 206 may be configured to execute varioussoftware applications, algorithms, and/or other suitable programs.External computing device 206 may be implemented as any suitable type ofdevice to facilitate the functionality as described herein. For example,external computing device 206 may be implemented as a network server, aweb-server, a database server, one or more databases and/or storagedevices, or any suitable combination thereof. Although illustrated as asingle device in FIG. 2, one or more portions of external computingdevice 206 may be implemented as one or more storage devices that arephysically co-located with external computing device 206, or as one ormore storage devices utilizing different storage locations as a shareddatabase structure (e.g. cloud storage).

In some embodiments, external computing device 206 may be configured toperform any suitable portion of the processing functions remotely thathave been outsourced by one or more of mobile computing devices 204.1and/or 204.2. For example, mobile computing device 204.1 and/or 204.2may collect data (e.g., geographic location data and/or telematics data)as described herein, but may send the data to external computing device206 for remote processing instead of processing the data locally. Insuch embodiments, external computing device 206 may receive and processthe data to determine whether an anomalous condition exists and, if so,whether to send an alert notification to one or more mobile computingdevices 204.1 and 204.2.

In one aspect, external computing device 206 may additionally oralternatively be part of an insurer computing system (or facilitatecommunications with an insurer computer system), and as such may accessinsurer databases, execute algorithms, execute applications, accessremote servers, communicate with remote processors, etc., as needed toperform insurance-related functions. For example, external computingdevice 206 may facilitate the receipt of telematics data or other datafrom one or more mobile computing devices 204.1-204.N and/or one or morevehicles 202.1-202.N, which may be associated with insurance customersand/or running a Telematics App, as further discussed below withreference to FIG. 3.

In aspects in which external computing device 206 facilitatescommunications with an insurer computing system (or is part of such asystem), data received from one or more mobile computing devices204.1-204.N and/or one or more vehicles 202.1-202.N may include logoncredentials which may be verified by external computing device 206 orone or more other external computing devices, servers, etc. These logoncredentials may be associated with an insurer profile, which mayinclude, for example, insurance policy numbers or other insurance policyinformation, a description and/or listing of insured assets, vehicleidentification numbers of insured vehicles, addresses of insuredstructures, contact information, premium rates, discounts, etc.

In this way, data received from one or more mobile computing devices204.1-204.N and/or one or more vehicles 202.1-202.N may allow externalcomputing device 206 to uniquely identify each insured customer and/orwhether each identified insurance customer has installed the TelematicsApp. Furthermore, any data collected from one or more mobile computingdevices 204.1-204.N may be referenced to each insurance customer and/orany insurance policies associated with each insurance customer forvarious insurance-related purposes.

For example, as further discussed below with reference to FIGS. 3 and 5,the one or more mobile computing devices 204.1-204.N and/or one or morevehicles 202.1-202.N may broadcast, in addition to or as part of thetelematics data, data indicative of whether a Telematics App has beeninstalled and/or usage data indicative of how often a driver uses thefunctionality associated with the Telematics App while driving. That is,similar or identical data may be received from a vehicle as opposed tothe mobile computing device located in the vehicle. In this way, thesame functions discussed below with reference to FIG. 3 regarding theTelematics App installed and executed on a mobile computing device mayalso (or alternatively) be installed and executed as part of a vehicle'sintegrated computer functions, as previously discussed with reference toFIG. 1 above and further discussed with reference to FIG. 5 below.

In various aspects, an insurer may leverage data regarding whether aninsured customer has installed a Telematics App or how often theTelematics App is used while driving to calculate, adjust, and/or updatevarious insurance pricing for an automotive insurance policy or othersuitable insurance policy. For example, an insurer may adjust insurancepremiums, rates, discounts, points, programs, etc., based upon theinsured having the functionality discussed herein and/or the amount thatthe insured uses the functionality discussed herein.

In addition, external computing device 206 may facilitate thecommunication of the updated insurance policies, premiums, rates,discounts, etc., to insurance customers for their review, modification,and/or approval—such as via wireless communication or data transmissionto one or more mobile computing devices 204.1-204.N and/or one or morevehicles 202.1-202.N. For example, an insurer may provide an initialdiscount for an insured customer installing the Telematics App andlogging in with the Telematics App. To continue this example, becausethe alert notifications provided by the Telematics App may reduce thelikelihood of a collision or other damage occurring to the vehicle orthe driver, use of the Telematics App may function to mitigate orprevent driving risks upon which an insurance policy is partially based.Therefore, an insurer may provide an additional discount that increaseswith the insured customer's usage of the Telematics App while driving.

In some aspects, any of mobile computing devices 204.1-204.N, vehicles202.1-202.N, external computing device 206, and/or infrastructurecomponent 208 may facilitate indirect communications between one or moreother mobile computing devices 204.1-204.2, vehicles 202.1-202.N,external computing device 206, and/or infrastructure component 208 vianetwork 201 or another suitable communication network and/or wirelesslink. For example, external computing device 206 may function as anintermediary device, receiving telematics data from an originatingmobile device 204.1 via radio link 203 b and relaying the telematicsdata to a destination mobile computing device 204.2 and/or to vehicle202.2 via radio link 203 c.

Infrastmcture component 208 may be implemented as any suitable type oftraffic infrastructure component configured to receive communicationsfrom and/or to send communications to other devices, such as mobilecomputing devices 204.1, 204.2 and/or external computing device 206, forexample. For example, infrastructure component 208 may be implemented asa traffic light, a railroad crossing light, a construction notificationsign, a roadside display configured to display messages, an electronictoll booth, a billboard display, etc.

In some aspects, infrastructure component 208 may be implemented as oneor more “smart” infrastructure components, which may be configured tocommunicate with one or more other devices directly and/or indirectly.Examples of smart infrastructure components may include, for example,smart stop signs, smart street signs, smart toll booths, smart road-sideequipment, smart markers, smart reflectors, smart billboard displays,etc. To provide an illustrative example, infrastructure component 208may be configured to communicate directly with mobile computing device204.2 via link 203.d and/or with mobile computing device 204.1 via links203 b and 203 f utilizing network 201. To provide another illustrativeexample, infrastructure component 208 may communicate with externalcomputing device 206 via links 203 e and 203 f utilizing network 201.

As discussed above, one or more infrastructure components 208 mayfacilitate indirect communications between one or more of mobilecomputing devices 204.1-204.N, vehicles 202.1-202.N, and/or externalcomputing device 206 via network 201 or another suitable communicationnetwork and/or wireless link. For example, one or more infrastructurecomponents 208 may function as an intermediary device, receivingtelematics data from an originating mobile computing device 204.2 and/orvehicle 202.2 via radio link 203 d and relaying the telematics data to adestination mobile computing device 204.1 and/or to vehicle 202.1 viaradio links 203 b and 203 f.

In some aspects, infrastructure component 208 may be configured toreceive geographic location data and/or telematics data from one or moreother devices and to process this data to determine whether an anomalouscondition has been detected and whether the detected anomalous conditionsatisfies a threshold distance condition with respect to infrastructurecomponent 208. The threshold distance condition may include, forexample, the geographic location of the anomalous condition being withina threshold radius of infrastructure component 208, on the same roadserviced by infrastructure component 208, etc. If so, infrastructurecomponent 208 may perform one or more relevant actions such asdisplaying one or more relevant messages to notify drivers in thevicinity, to modify traffic patterns, to change traffic light timing, toredirect traffic, etc.

In other aspects, infrastructure component 208 may receive dataindicating that an alert is to be generated and/or the type of alertthat is to be generated. In accordance with such aspects, one or more ofmobile computing devices 204.1, 204.2 and/or external computing device206 may make the determination of whether an anomalous condition existsand is within a threshold distance of infrastructure component 208. Ifso, the data received by infrastructure component 208 may be indicativeof the type of anomalous condition, the location of the anomalouscondition, commands to cause infrastructure component 208 to perform oneor more acts, the type of acts to perform, etc.

To provide some illustrative examples, if infrastructure component 208is implemented as a smart traffic light, infrastructure component 208may change a traffic light from green to red (or vice-versa) or adjust atiming cycle to favor traffic in one direction over another. To provideanother example, if infrastructure component 208 is implemented as atraffic sign display, infrastructure component 208 may display a warningmessage that the anomalous condition (e.g., a traffic accident) has beendetected ahead and/or on a specific road corresponding to the geographiclocation data.

In additional aspects, other vehicles may play a role in the one or morealert notifications. To provide an illustrative example, an emergencyvehicle (e.g., an ambulance, fire truck, etc.) may be dispatched to thescene of an accident. In such a case, the emergency vehicle may beconfigured to broadcast one or more signals that cause one or more ofmobile computing devices 204.1-204.2 to generate one or more alertnotifications and/or infrastructure component 208 to change to adifferent state. These signals may be broadcasted from a mobilecomputing device carried by emergency response personnel and triggeredupon the vehicle approaching (e.g., within a threshold distance) ageographic location associated the vehicle accident. Additionally oralternatively, the signals may be broadcasted by any suitable devicemounted in or otherwise associated with the emergency response vehicle.

To provide another illustrative example, a train may broadcast one ormore signals indicating that the train is approaching a railroadcrossing, which is received by one or more of mobile computing devices204.1-204.2 and/or infrastructure component 208 and results in themobile computing devices generating one or more alert notificationsand/or the infrastructure component 208 changing to a different state.Similar to the emergency vehicle example above, the broadcasted signalmay be transmitted upon the train approaching (e.g., within a thresholddistance) of the crossing location, and may be transmitted from a mobilecomputing device and/or equipment mounted on or otherwise associatedwith the train.

Additional vehicles such as emergency response vehicles and trains arenot illustrated in FIG. 2 for purposes of brevity. However, the signalstransmitted from these vehicles may be transmitted in accordance withany suitable communication protocol directly and/or indirectly to one ormore or mobile computing devices 204.1-204.2 and/or infrastructurecomponent 208. For example, the signals may be transmitted to directlyto infrastructure component 208, indirectly to one more mobile computingdevices 204.1-204.2 via network 201 and/or remote computing device 206,etc.

Exemplary End-User/Destination Devices

The following details regarding the determination of an anomalouscondition are explained in this section with reference to computingdevice 300, which may be a mobile computing device or “mobile device”(e.g., smart phone, laptop, tablet, phablet, smart watch, wearableelectronics, etc.). In the present aspect, computing device 300 may beimplemented as any suitable computing device, such as a mobile computingdevice (e.g., mobile computing device 100, as shown in Figure land/orone of mobile computing devices 204.1-204.N, as shown in FIG. 2). Inanother aspect, computing device 300 may be implemented as an on-boardvehicle computer (e.g., on-board vehicle computer 114, as shown in FIG.1). In still other aspects, computing device 300 may be implemented as adevice external to a vehicle (e.g., remote computing device 206 orinfrastructure component 208, as shown in FIG. 2).

In aspects in which computing device 300 is associated with a vehicle(e.g., a mobile computing device located in a vehicle or integrated aspart of the vehicle itself) computing device 300 may be associated witha driver of the vehicle. In some instances, the driver may drive thevehicle, while in other aspects the vehicle may perform autonomous orsemi-autonomous driving functions, which are further discussed belowwith reference to FIG. 5. In any event, when an anomalous condition(e.g., a travel event, traffic event, etc.) is identified by computingdevice 300, computing device 300 may execute various corrective orpreventive actions.

The determination of the type of preventive or corrective action to takemay be based upon, for example, the type of anomalous condition, thetype of destination vehicle (e.g., whether the vehicle may engage inautonomous driving, whether the vehicle is a smart vehicle, etc.),and/or the capabilities of the destination vehicle. For example, as willbe further discussed below, computing device 300 may generate an alert,calculate an alternate travel route that avoids the location of theanomalous condition, calculate driving directions for the vehicle inwhich computing device 300 is located to travel along the alternatetravel route, autonomously re-route the vehicle in which computingdevice 300 is implemented, etc.

Furthermore, depending upon the implementation of computing device 300,the methods and processes utilized to determine the existence ofanomalous conditions may be performed locally, remotely, or any suitablecombination of local and remote processing techniques.

FIG. 3 illustrates a block diagram of an exemplary computing device 300in accordance with an exemplary aspect of the present disclosure.Computing device 300 may be implemented as any suitable computing deviceconfigured to (1) monitor, measure, generate, and/or or collecttelematics data; (2) broadcast the geographic location data and/or thetelematics data to one or more external components, such as via wirelesscommunication and/or data transmission; (3) receive geographic locationdata and/or telematics data and/or other data (e.g., notifications,telematics-related messages, etc. broadcasted from another device, suchas via wireless communication and/or data transmission; (4) determinewhether an anomalous condition exists at the geographic locationindicated by the geographic location data based upon the telematicsdata, geographic location data, and/or other data; (5) generate one ormore alerts indicative of the anomalous condition, and/or (6) broadcastone or more alert notifications to other devices, such as via wirelesscommunication and/or data transmission.

Computing device 300 may include a display 316, a graphics processingunit (GPU) 318, a location acquisition unit 320, a speaker/microphone322, a sensor array 326, a user interface 328, a communication unit 330,and/or a controller 340.

In one aspect, controller 340 may include a program memory 302, amicroprocessor (MP) 306, a random-access memory (RAM) 308, and/or aninput/output (I/O) interface 310, each of which may be interconnectedvia an address/data bus 312. Controller 340 may be implemented as anysuitable type and/or number of processors, such as a host processor forthe relevant device in which computing device 300 is implemented, forexample. In some aspects, controller 340 may be configured tocommunicate with additional data storage mechanisms that are not shownin FIG. 3 for purposes of brevity (e.g., one or more hard disk drives,optical storage drives, solid state storage devices, etc.) that residewithin or are otherwise associated with mobile computing device 300.

Program memory 302 may be implemented as any suitable number and/or typeof memory unit configured to store data used in conjunction with one ormore functions performed by computing device 300, which may facilitatethe interaction between computing device 300 and one or more otherdevices. For example, if computing device 300 is implemented as a mobilecomputing device (e.g., mobile computing device 204.1, as shown in FIG.2), then program memory 302 may store one or more programs,applications, algorithms, etc. that, when executed by controller 340,facilitate the interaction between computing device 300 and (i) one ormore networks (e.g., network 201), (ii) other mobile computing devices(e.g., mobile computing device 204.2), (iii) external computing devices(e.g., external computing device 206), (iv) vehicles (e.g., vehicle108), (v) vehicle on-board computers (e.g., on-board computer 114, asshown in FIG. 1 and/or smart vehicle control system 500, which isfurther discussed below with reference to FIG. 5), infrastructurecomponents (e.g., infrastructure component 208), etc.

In various aspects, program memory 302 may be implemented as anon-transitory tangible computer readable media configured to storecomputer-readable instructions, that when executed by controller 340,cause controller 340 to perform various acts. Program memory 302 mayinclude an operating system 342, one or more software applications 344,and one or more software routines 352. To provide another example,program memory 302 may include other portions to store data that may beread from and written to by MP 306, such as data storage 360, forexample.

One or more MPs 306 may be configured to operate in conjunction with oneor more of display 316, communication unit 330, GPU 318, locationacquisition unit 320, speaker/microphone 322, user interface 328, sensorarray 326, 1/O block 310, RAM 308, and/or program memory 302 to processand/or analyze data, to store data to program memory 302, to retrievedata from program memory 302, and/or to perform one or moreinsurance-related and/or telematics data-based functions.

For example, one or more MPs 306 and/or communication unit 330 mayfacilitate receiving data from and/or sending data to one or more otherdevices. For example, with reference to FIG. 2, one or more MPs 306and/or communication unit 330 may facilitate sending data to and/orreceiving data from one or more mobile computing devices 204.1-204.N,one or more vehicles 202.1-202.N, external computing device 206, one ormore infrastructure components 208, etc. To facilitate thisfunctionality, one or more MPs 306 may be coupled via one or more wiredand/or wireless interconnections to one or more other components ofcomputing device 300, such as via any suitable number of data and/oraddress buses, for example. These interconnections are not shown in FIG.3 for purposes of brevity.

In one aspect, one or more MPs (micro-processors) 306 may be configuredto execute one or more of software applications 344, software routines352 residing in program memory 302, and/or other suitable softwareapplications. For example, operating system 342 may be implemented asany suitable operating system platform depending upon the particularimplementation of computing device 300. For example, if computing device300 is implemented as a mobile computing device, operating system 342may be implemented as a mobile OS platform such as the iOS®, Android™,Palm® webOS, Windows® Mobile/Phone, BlackBerry® OS, or Symbian® OSmobile technology platforms, developed by Apple Inc., Google Inc., PalmInc. (now Hewlett-Packard Company), Microsoft Corporation, Research inMotion (RIM), and Nokia, respectively.

In one embodiment, data storage 360 may store data such as applicationdata for the one or more software applications 344, routine data for theone or more software routines 352, geographic location data and/ortelematics data, etc.

Display 316 may be implemented as any suitable type of display and mayfacilitate user interaction with computing device 300 in conjunctionwith user interface 328. For example, display 316 may be implemented asa capacitive touch screen display, a resistive touch screen display,etc. In various embodiments, display 316 may be configured to work inconjunction with controller 340 and/or GPU 318 to display alerts and/ornotifications received from other devices indicative of detectedanomalous conditions.

Communication unit 330 may be configured to facilitate communicationsbetween computing device 300 and one or more other devices, such asother mobile computing devices, networks, external computing devices,smart infrastructure components, etc. To accomplish this, communicationunit 330 may be implemented with any suitable number and/or type ofhardware components such as, for example, one or more transceivers,receivers, transmitters, antennas, ports, etc.

As previously discussed with reference to FIGS. 1 and 2, computingdevice 300 may be configured to communicate with these other devices inaccordance with any suitable number and type of communication protocols.Thus, in various aspects, communication unit 330 may be configured tosupport any suitable number and type of communication protocols basedupon a particular network and/or device in which computing device 300 iscommunicating to facilitate this functionality.

Communication unit 330 may be configured to support separate orconcurrent communications, which may be the same type of communicationprotocol or different types of communication protocols. For example,communication unit 330 may be configured to facilitate communicationsbetween computing device 300 and an external computing device (e.g.,external computing device 206) via cellular communications whilefacilitating communications between computing device 300 and the vehiclein which it is carried (e.g., vehicle 108) via BLUETOOTH communications.

Communication unit 330 may be configured to broadcast data and/or toreceive data in accordance with any suitable communications schedule,which may be periodic (e.g., recurring) or aperiodic (e.g., transmittedwhen a memory buffer is full of collected telematics data, transmittedonce an anomalous condition is identified, etc.). For example,communication unit 330 may be configured to broadcast geographiclocation data and/or telematics data every 15 seconds, every 30 seconds,every minute, etc.

The data received by computing device 300 may include any suitable typeof data without departing from the spirit and scope of the aspectsdescribed herein. For example, communication unit 330 may facilitatecomputing device 300 receiving telematics data, geographic locationdata, and/or other telematics-related data (alert notifications,telematics-related messages, etc.) that is transmitted from anotherdevice.

As will be further discussed below, the geographic location data and/ortelematics data may be sampled in accordance with any suitable samplingperiod. Thus, when broadcasted by communications unit 330 in accordancewith a recurring schedule, the geographic location data and/ortelematics data may include a log or collection of the geographiclocation data and/or telematics data that was sampled since the lastdata transmission. A suitable communication schedule may be selected asa tradeoff between a desired anomalous condition detection speed andbattery usage of computing device 300, when applicable.

Additionally or alternatively, aspects include communication unit 330being configured to conditionally send data, which may be particularlyadvantageous when computing device 300 is implemented as a mobilecomputing device, as such conditions may help reduce power usage andprolong battery life. For example, communication unit 330 may beconfigured to only broadcast when telematics data has been sampled sincethe last transmission, which will be further discussed below withregards to sensor array 326. Controller 340 may determine whether hasbeen sampled since the last transmission by, for example, analyzing amemory address range (e.g., in data storage 360, RAM 308, etc.)associated with the storage of the telematics data and comparing thecontents of this buffer to a known range of valid values.

To provide another example, aspects include communication unit 330 beingadditionally or alternatively configured to only broadcast telematicsdata when computing device 300 is connected to a power source (e.g., anin-vehicle charger). To provide still another example, aspects includecommunication unit 330 being additionally or alternatively configured toonly broadcast telematics data when communication unit 330 is connectedto and/or communicating with a device identified as a vehicle. This mayinclude, for example, identifying a BLUETOOTH connection as a validvehicle to satisfy this condition upon installation and/or setup of therelevant application or program executed by computing device 300 tofacilitate the functionality described herein.

Location acquisition unit 320 may be configured to generate geographiclocation data utilizing any suitable global positioning techniques. Forexample, location acquisition unit 320 may communicate with one or moresatellites and/or wireless transmitters to determine a location ofcomputing device 300. Location acquisition unit 320 may use “AssistedGlobal Positioning System” (A-GPS), satellite GPS, or any other suitableglobal positioning protocol (e.g., the GLONASS system operated by theRussian government, the Galileo system operated by the European Union,etc.) to determine a geographic location of computing device 300.

In one aspect, location acquisition unit 320 may periodically store oneor more geographic locations of computing device 300 as geographiclocation data in any suitable portion of memory utilized by computingdevice 300 (e.g., program memory 302, RAM 308, etc.) and/or to anotherdevice (e.g., another mobile computing device, an external computingdevice, etc.). In this way, location acquisition unit 320 may sample thelocation of computing device 300 in accordance with any suitablesampling rate (e.g., every 5 seconds, 10 seconds, 30 seconds, etc.) andstore this geographic location data representing the position ofcomputing device 300, and thus the vehicle in which it is travelling,over time.

Speaker/microphone 322 may be configured as one or more separatedevices. Speaker/microphone 322 may include a microphone configured todetect sounds and to convert sounds to data suitable for communicationsvia communications unit 330. Speaker/microphone 322 may additionally oralternatively include a speaker configured to play sound in response todata received from one or more components of computing device 300 (e.g.,controller 340). In one embodiment, speaker/microphone 322 may beconfigured to play audible alerts.

User-interface 328 may be implemented as any suitable device configuredto collect user input, such as a “soft” keyboard displayed on display316 of computing device 300, a keyboard attached to computing device300, an external keyboard communicating via a wired or a wirelessconnection (e.g., a BLUETOOTH keyboard), an external mouse, etc.

Sensor array 326 may be configured to measure any suitable number and/ortype of sensor metrics as part of the telematics data. In one aspect,sensor array 326 may be implemented as one or more sensors positioned todetermine the speed, force, heading and/or direction associated withmovements of computing device 300 and, thus, a vehicle in whichcomputing device 300 is positioned. Additionally or alternatively,sensor array 326 may be configured to communicate with one or moreportions of computing device 300 to measure, collect, and/or generateone or more sensor metrics from one or more non-sensor sources, whichwill be further discussed below.

To generate one or more sensor metrics, sensor array 326 may include,for example, one or more cameras, accelerometers, gyroscopes,magnetometers, barometers, thermometers, proximity sensors, lightsensors, Hall Effect sensors, etc. In aspects in which sensor array 326includes one or more accelerometers, sensor array 326 may be configuredto measure and/or collect accelerometer metric values utilizing anX-axis, Y-axis, and Z-axis accelerometer. In accordance with suchaspects, sensor array 326 may measure sensor metric values as athree-dimensional accelerometer vector that represents the movement ofcomputing device 300 in three dimensional space by combining the outputsof the X-axis, Y-axis, and Z-axis accelerometers using any suitabletechniques.

In one aspect, sensor array 326 may include one or more cameras or otherimage capture devices. In accordance with such aspects, the one or morecameras that are part of sensor array 326 may be mounted or otherwisepositioned on mobile computing device 300 such that, when mobilecomputing device 300 is docked, cradled, or otherwise mounted within avehicle, images may be captured from this vantage point. For example,when mobile computing device 300 is mounted within a vehicle, a cameraimplemented by sensor array 326 may function as a dashboard camera,capturing images and/or video data of various objects outside of thevehicle from this vantage point. Additionally or alternatively, mobilecomputing device 300 may capture audio data with the image and/or videodata via speaker/microphone 322.

In various aspects, mobile computing device 300 may begin to capturedata upon detecting that it has been placed in a cradle, and otherwisenot capture data in such a manner. This detection may occur, forexample, via one or more conditions being satisfied. For example, mobilecomputing device 300 may utilize one or more sensors (e.g., anaccelerometer that is part of sensor array 326) to determine that mobilecomputing device 300 has changed orientation to horizontal (as is commonwhen docked in a vehicle), that mobile computing device 300 iscommunicating via BLUETOOTH with the vehicle, that the vehicle is movingabove a threshold speed, etc. Aspects include any suitable number ofconditions, upon being satisfied, triggering mobile computing device 300to start collecting telematics data, images, audio, video, etc., viasensor array 326.

In various aspects, sensor array 326 may be configured to sample the oneor more sensor metrics in accordance with any suitable sampling rateand/or based upon one or more conditions being satisfied. For example,sensor array 326 may be configured to implement one or moreaccelerometers to sample sensor metrics indicative of a g-forceassociated with vehicle braking, acceleration, and cornering at a rateof 15 Hz, 30 Hz, 60 Hz, etc., which may be the same sampling rate as oneanother or different sampling rates. To provide another example, sensorarray 326 may be configured to implement one or more gyroscopes toimprove the accuracy of the measured one or more sensor metrics and todetermine whether the phone is in use or stationary within a vehicle. Toprovide another example, sensor array 326 may implement a compass(magnetometer) to determine a direction or heading of a vehicle in whichcomputing device 300 is located. Additional examples of sensor metricsmay be those applicable to the determination of a current lane thevehicle is in, which may be derived, for example, via an image analysisof image and/or video data obtained via one or more cameras that may beintegrated as part of sensor array 326.

Again, sensor array 326 may additionally or alternatively communicatewith other portions of computing device 300 to obtain one or more sensormetrics even though these sensor metrics may not be measured by one ormore sensors that are part of sensor array 326. For example, sensorarray 326 may communicate with one or more of location acquisition unit320, communication unit 330, and/or controller 340 to obtain data suchas timestamps synchronized to the sampling of one or more sensor metrics(which may be measured to within hundredths of a second or smallerresolutions), geographic location data (and correlated timestampsthereof), a velocity based upon changes in the geographic location dataover time, a battery level of computing device 300, whether a battery ofcomputing device 300 is charging, whether computing device 300 is beinghandled or otherwise in use, an operating status of computing device 300(e.g., whether computing device 300 is unlocked and thus in use).

In various aspects, sensor array 326 may base timestamps upon anysuitable clock source, such as one utilized by location acquisition unit320 for GNSS functions. The timestamps may be, for example, recorded orlogged as various data is sampled to be synchronized to the sampling ofone or more sensor metrics (which may be measured to within hundredthsof a second or smaller resolutions).

Additionally or alternatively, sensor array 326, location acquisitionunit 320, and/or communication unit 330 may log or otherwise measurevarious metrics or other data that may be used by controller 340 todetermine usage metrics such as how often the functionality of theTelematics Application is being utilized when a vehicle is being driven.For example, sensor array 326 may log the time when telematics data isbeing collected, when the Telematics Application is running and/or whenthe Telematics Application has been started. To provide additionalexamples, communication unit 330 may store data indicative of aBLUETOOTH connection status of mobile computing device 300. To provideyet another example, location acquisition unit 320 may store and/or logthe changes in geographic location of mobile computing device 300 overtime.

In various aspects, controller 340 may determine how often a driver usesthe Telematics App based upon any suitable combination of theaforementioned data. For example, the BLUETOOTH connection status may beleveraged to determine whether mobile computing device 300 is located ina vehicle. To provide another example, the changes in the geographiclocation data over time may be utilized to determine whether mobilecomputing device 300 has exceeded a threshold speed for a thresholdduration of time. In this way, a determination may be made whethermobile computing device 300 is located in a vehicle while the vehicle isbeing driven.

Various aspects include the aforementioned data being leveraged tocalculate a usage amount in which a user utilizes the Telematics Appwhile driving. For example, the usage amount may be based upon a totalproportion of time (e.g., 80% of the time while driving, thefunctionality provided by the Telematics App is enabled). To provideanother example, the usage amount may be mileage-based (e.g., 90% of themiles driven are done so with the functionality of the Telematics Appavailable to the driver). As discussed above, this usage data may besent to an insurer or other third party via a telematics datatransmission or a separate transmission and used to set and/or adjust aninsurance policy, premium, or discount for the insured customer.

In one aspect, sensor array 326 may sample one or more sensor metricsbased upon one or more conditions being satisfied. For example, sensorarray 326 may determine, based upon gyroscope sensor metrics,communication with controller 340, etc., whether computing device 300 isin use. If computing device 300 is in use (e.g., when implemented as amobile computing device) then the movement of computing device 300within the vehicle may not truly represent the vehicle motion, therebycausing sensor metrics sampled during this time to be erroneous.Therefore, aspects include sensor array 326 sampling the one or moresensor metrics when computing device 300 is not in use, and otherwisenot sampling the one or more sensor metrics.

In one aspect, sensory array 326 may include one or more cameras and/orimage capture devices. When sensory array 326 is implemented with one ormore cameras, these cameras may be configured as any suitable type ofcamera configured to capture and/or store images and/or video. Forexample, when mobile computing device 300 is mounted in a vehicle, thecamera may be configured to store images and/or video data of the roadin front of the vehicle in which it is mounted, and to store this datato any suitable portion of program memory 302 (e.g., data storage 360).Controller 340 and/or MP 306 may analyze this data to generate one ormore local alerts, to transmit signals indicative of detected alters toone or more other devices, etc., which is further discussed below withreference to the execution of anomalous condition detection routine 358.

Again, the telematics data broadcasted by computing device 300 mayinclude one or more sensor metrics. However, the telematics data mayadditionally or alternatively include other external data that may berelevant in determining the presence of an anomalous condition. Forexample, the telematics data may include external data such as speedlimit data correlated to a road upon which computing device 300 islocated (and thus the vehicle in which it is travelling), an indicationof a type of road, a population density corresponding to the geographiclocation data, etc.

In some aspects, computing device 300 may obtain this external data byreferencing the geographic location data to locally stored data (e.g.,data stored in data storage 360) and broadcasting this data appended toor otherwise included with the sensor metrics data as part of thetelematics data. In other aspects, the device receiving the telematicsdata (e.g., a mobile computing device, an external computing device, aninfrastructure component) may generate the external data locally or viacommunications with yet another device. As will be further discussedbelow, this external data may further assist the determination ofwhether an anomalous condition is present.

In some aspects, software applications 344 and/or software routines 352may reside in program memory 302 as default applications that may bebundled together with the OS of computing device 300. For example, webbrowser 348 may be part of software applications 344 that are includedwith OS 342 implemented by computing device 300.

In other aspects, software applications 344 and/or software routines 352may be installed on computing device 300 as one or more downloads, suchas an executable package installation file downloaded from a suitableapplication store via a connection to the Internet. For example, alertnotification application 346, telematics collection routine 354,geographic location determination routine 356, and/or anomalouscondition detection routine 358 may be stored to suitable portions ofprogram memory 302 upon installation of a package file downloaded insuch a manner. Examples of package download files may include downloadsvia the iTunes store, the Google Play Store, the Windows Phone Store,downloading a package installation file from another computing device,etc. Once downloaded, alert notification application 346 may beinstalled on computing device 300 as part of an installation packagesuch that, upon installation of alert notification application 346,telematics collection routine 354, geographic location determinationroutine 356, and/or anomalous condition detection routine 358 may alsobe installed.

In one embodiment, software applications 344 may include an alertnotification application 346, which may be implemented as a series ofmachine-readable instructions for performing the various tasksassociated with executing one or more embodiments described herein Inone aspect, alert notification application 346 may cooperate with one ormore other hardware or software portions of computing device 300 tofacilitate these functions.

In one aspect, alert notification application 346 may function as aTelematics Application (or “App”) which is downloaded and installed onmobile computing device (or mobile device) 300 by a user via a suitablethird-party software store and/or portal (e.g., Apple iTunes, GooglePlay, the Windows Store, etc.).

To provide an illustrative example, alert notification application 344may include instructions for performing tasks such as determining ageographic location of computing device 300 (e.g., via communicationswith location acquisition unit 330), monitoring, measuring, generatingand/or collecting telematics data, broadcasting the geographic locationdata and/or the telematics data to one or more external devices,receiving geographic location data and/or telematics data from anothercomputing device, determining whether an anomalous condition existsbased upon the geographic location data and/or the telematics data,generating one or more alerts indicative of the determined anomalouscondition, receiving user input, facilitating communications betweencomputing device 300 and one or more other devices in conjunction withcommunication unit 330, etc.

To provide another example, aspects include mobile computing device 300being configured to capture image and/or video data while cradled in adock or otherwise mounted within a vehicle, as previously discussed. Inaccordance with various aspects, this data capture may be facilitated,for example, by instructions stored in alert notification application346 being executed by controller 340 and/or MP 306. Thus, in variousaspects, alert notification application 346 may facilitate mobilecomputing device 300 capturing image, audio, and/or video data at anysuitable sampling rate (e.g., once every second, 5 times per second,etc.) and storing this data to any suitable portion of the mobilecomputing device (e.g., data storage 360). Aspects include data samplingprocesses occurring as background operations to allow other applicationsto be run on mobile computing device 300 (e.g., navigation applications)while telematics data and/or images, video, and/or audio data iscollected by mobile computing device 300.

Software applications 344 may include a web browser 348. In someembodiments (e.g., when computing device 300 is implemented as a mobilecomputing device), web browser 348 may be a native we browserapplication, such as Apple's Safari®, Google Android™ mobile webbrowser, Microsoft Internet Explorer® for Mobile, Opera Mobile™, etc. Inother embodiments, web browser 348 may be implemented as an embedded webbrowser.

Regardless of the implementation of web browser 348, various aspectsinclude web browser 348 being implemented as a series ofmachine-readable instructions for interpreting and displaying web pageinformation received from an external computing device (e.g., externalcomputing device 204.2, as shown in FIG. 2). This web page informationmay be utilized in conjunction with alert notification application 346to perform one or more function of the aspects as described herein.

In one embodiment, software routines 352 may include a telematicscollection routine 354. Telematics collection routine 354 may includeinstructions, that when executed by controller 340, facilitate sampling,monitoring, measuring, collecting, quantifying, storing, encryptingtransmitting, and/or broadcasting of telematics data. In some aspects,telematics collection routine 354 may facilitate collection oftelematics data locally via one or more components of computing device300 (e.g., via sensor array 326, location acquisition unit 320,controller 340, etc.). In other aspects, telematics collection routine354 may facilitate the storage of telematics data received from anotherdevice (e.g., via communication unit 330).

In one aspect, telematics collection routine 354 may work in conjunctionwith controller 340 and/or alert notification application 346 toperiodically listen for and/or to periodically broadcast telematicsdata. For example, controller 340 may, upon executing alert notificationapplication 346, periodically listen for a broadcast containingtelematics data generated and transmitted from other mobile computingdevices, vehicles, external computing devices, and/or infrastructurecomponents. Upon detecting a broadcast, controller 340 may download thebroadcast to a suitable portion of memory unit 302 and analyze thetelematics data contained therein for potential traffic events, travelevents, alerts, messages, etc. Such aspects may be particularly useful,for example, to save battery life of the mobile computing device, ascontinuous listening is not necessary but instead may be performed, forexample, in accordance with a particular timing schedule.

To provide another example, controller 340 may, upon executing alertnotification application 346, periodically broadcast telematics data,which may be received by other mobile computing devices, vehicles,external computing devices, and/or infrastructure components. To providean illustrative example, the telematics data may be sampled, updated,and/or broadcasted in accordance with a periodically recurring scheduleor sampling rate (e.g., five times per second, every second, once every5 seconds, once every ten seconds, etc.) when a Telematics App installedon a mobile computing device is executed.

In one embodiment, software routines 352 may include a geographiclocation determination routine 356. Geographic location determinationroutine 356 may include instructions, that when executed by controller340, facilitate sampling measuring, collecting quantifying, storing,transmitting and/or broadcasting of geographic location data (e.g.,latitude and longitude coordinates). In some aspects, geographiclocation determination routine 356 may facilitate generating and/orstoring geographic location data locally via one or more components ofcomputing device 300 (e.g., via location acquisition unit 320 and/orcommunication unit 330). In other aspects, geographic locationdetermination routine 356 may facilitate the storage of geographiclocation data received from another device (e.g., via communication unit330).

Additionally or alternatively, software routines 352 may includeanomalous condition detection routine 358. Anomalous condition detectionroutine 358 may include instructions, that when executed by controller340, facilitate the determination of whether an anomalous conditionexists based upon the telematics data, the geographic location data, oneor more telematics-related messages included in a received telematicsdata transmission (e.g., transmitted by another mobile computing device,smart infrastructure, another vehicle, etc.), and/or image and/or videodata captured by one or more cameras or other imaging devices.

An anomalous condition may include any suitable condition that indicatesa deviation from normal traffic patterns or otherwise poses a potentialhazard or inconvenience to other drivers. In various aspects, ananomalous condition may be detected based upon an analysis of locallygenerated or collected telematics data, telematics data received fromanother computing device via communication unit 330, an analysis of datatransmitted with and/or included as part of a telematics data broadcastor transmission, an analysis of one or more received telematics-relatedmessages (e.g., alert notifications), etc.

For example, MP 306 may execute instructions stored in anomalouscondition detection routine 358 to determine or identify whether atravel event exists associated with telematics data received from anoriginating device or vehicle, a GPS location or other location of thetravel event, whether the telematics data includes a message indicatingthe existence of the travel event, an estimated or actual geographicalor temporal scope of the travel event from an analysis of telematicsdata, etc. In other words, computing device 300 may analyze thetelematics data itself and/or any suitable portion of the transmissionin which the telematics data is sent to attempt to identify an alert,location, indication, and/or message regarding a travel event or otheranomalous condition that has already been identified by another device.For example, the telematics data (or other data sent with the telematicsdata as part of a data transmission) may include a message or otherinformation indicating a type of anomalous condition or travel event,when it was detected, and its geographic location.

To provide another example, the telematics data or telematics datatransmission may include information that identifies the nature,severity, and/or area of impact of a travel event or other anomalouscondition. This information may thus identify the travel event or otheranomalous condition that the mobile computing device, smartinfrastructure, or vehicle has encountered or is presently encounteringComputing device 300 may then use such information to identify thetravel event at that location and/or to take or direct corrective orpreventive action to facilitate safer vehicle travel for the movingvehicle in which computing device 300 is located. For example, computingdevice 300 may generate, display, and/or provide an alert for the driverof the moving vehicle in which computing device 300 is located, which isfurther discussed below.

To provide an illustrative example, if an accident occurs, traffic mayslow down due to a car pileup, a reduction in available lanes, and/orrerouting of traffic. Because the telematics data may include dataindicative of the speed limit at the location corresponding to thegeographic location where the telematics data was sampled, a comparisonbetween the speed of computing device 300 and the posted or other speedlimit data (such as a comparison between mobile device or vehicle speedwith a map of and/or known, posted speed limit information) may indicatean anomalous condition. Furthermore, because each vehicle may sampleand/or broadcast geographic location data and/or telematics data in realtime, the anomalous conditions may be detected with minimal delay asthey occur.

Although the speed of the vehicle may indicate an anomalous condition,aspects include other types of anomalous conditions being detected basedupon the telematics data. For example, an anomalous condition may beidentified when the one or more sensor metrics indicate that an airbaghas been deployed, and thus the vehicle associated with computing device300 has been in an accident. This may be determined, for example, via ananalysis of barometer readings matching a pressure versus time profileand/or via an indication from a dedicated airbag deployment sensorlocated in the vehicle.

To provide another example, an anomalous condition may be identifiedbased upon weather fluctuations associated with a rapid formation ofice, a sudden change from a paved to a dirt road, the triggering of acrash detection system, a threshold number of wheel slips and/or skidsbeing sampled within a threshold sampling period (indicating slipperyconditions), sensor metrics indicative of a rollover condition, a suddenstop (indicating a collision), a departure from the road (indicating apulled over vehicle), etc.

To provide another illustrative example based upon a traffic accident,if a first vehicle carrying a first computing device 300 is slowed downdue to a traffic accident, then the one or more sensor metrics sampledby sensor array 326 will indicate the speed of the first vehicle over aperiod of time. If the one or more sensor metrics indicate that thefirst vehicle's speed is below the speed limit by some threshold amountor proportion thereof (e.g., 20 mph in a 55 mph zone, 50% of the postedspeed limit, etc.) and this is maintained for a threshold duration oftime (e.g., 30 seconds, one minute, two minutes, etc.) then controller340 may, upon execution of anomalous condition detection routine 358,conclude that an anomalous condition has been detected. This anomalouscondition may also be correlated to the geographic location associatedwith the geographic location data due to synchronization between thegeographic location data and the sampled telematics data.

Further continuing this example, upon determination of the anomalouscondition, alert notification application 346 may broadcast anotification indicating the detected anomalous condition, the telematicsdata, and/or the geographic location data associated with the detectedanomalous condition. In one aspect, a second vehicle equipped with asecond computing device 300 may receive this data and further determinewhether the anomalous condition is relevant based upon the geographicrelationship between the first and second devices, which is furtherdiscussed below. If the anomalous condition is relevant, then the secondcomputing device 300 may generate an alert indicating the anomalouscondition.

To provide another example by modifying the details of the previous one,aspects may include computing device 300 broadcasting telematics dataand/or geographic location data but not notification data. In accordancewith such aspects, upon being received by a second computing device 300(e.g., a mobile computing device in a second vehicle, an externalcomputing device, a smart infrastructure component, etc.) the secondcomputing device 300 may determine the relevance of the anomalouscondition based upon the geographic relationship between itself and thefirst computing device 300.

If the second computing device 300 determines that an anomalouscondition, even if present, would be irrelevant or inapplicable basedupon the distance between these devices, the second computing device 300may ignore the telematics data, thereby saving processing power andbattery life. However, if the second computing device 300 determinesthat the geographic location data indicates a potentially relevantanomalous condition, the second computing device 300 may further processthe telematics data and take the appropriate corrective or preventiveaction if an anomalous condition is found (e.g., issue an alertnotification, generate an alert for the driver of the vehicle, display awarning message, etc.).

To provide yet another example by further modifying the details in theprevious two, aspects may include computing device 300 broadcasting thetelematics data and geographic location data to an external computingdevice (e.g., to external computing device 206 via network 201, as shownin FIG. 2). In addition, the second computing device 300 associated withthe second vehicle may likewise broadcast telematics data and geographiclocation data to the external computing device. In accordance with suchaspects, the external computing device may determine whether ananomalous condition exists and is relevant to each of the first andsecond devices 300 based upon a geographic relationship between thefirst and second devices 300. When relevant, external computing devicemay be configured to send alert notifications to the first and/or seconddevices 300, which may include any suitable type of communications suchas push notifications, a short messaging service (SMS) message, anemail, a notification that used in conjunction with the OS running oneach receptive computing device 300, etc. Upon receiving thenotification from the external computing device, the first and/or secondcomputing device 300 may generate an alert indicating a description ofthe anomalous condition and/or its location.

The geographic relationship between two or more devices 300 may beutilized in several ways to determine the relevance of the anomalouscondition and/or whether to take corrective or preventive action. Forinstance, current speed, location, route, destination, and/or directionof travel of a first vehicle (collecting and/or associated with thetelematics data) may be individually or collectively compared withcurrent speed, location, route, destination, and/or direction of travelof a second vehicle traveling on the road. As one example of thegeographic relationship, a first vehicle location (and associated with atravel or traffic event) may be compared with a second vehicle location,current route, and/or destination to determine whether the secondvehicle should divert course or slow down to alleviate the risk of thesecond vehicle being involved in a collision or a traffic jam (as aresult of the travel or traffic event that is identified by thetelematics data).

As another example of the geographic relationship, a radius from onevehicle or a line-of-sight distance between vehicles may be utilized andcompared to a threshold distance. For example, if computing device 300is implemented as an external computing device and determines aline-of-sight distance between a first and second vehicle to be lessthan a threshold distance (e.g., a half mile, one mile, etc.), then theexternal computing device may issue an alert notification to bothvehicles. In this way, an external computing device may act as an alertmanagement device, processing data and sending notifications to thosedevices for which a detected anomalous condition is relevant.

In another example of the geographic relationship, the geographiclocation data may be correlated with a map database to associate theanomalous condition with a road and to determine the relevance of theanomalous condition based upon other vehicles sharing the road. The mapdatabase may be stored, for example, in a suitable portion of computingdevice 300 (e.g., data storage 360) or retrieved via communications withone or more external computing devices. To provide an illustrativeexample, a computing device 300 may be implemented as an externalcomputing device. The external computing device may determine, fromtelematics data and geographic location data received from a firstcomputing device 300, that a first vehicle is located on a highway at acertain geographic location. If the external computing device determinesthat a second computing device 300 in a vehicle travelling on the samehighway is within a threshold distance approaching the first vehicle,then the external computing device may issue an alert notification tothe second vehicle.

In yet other aspects, the geographic location data may be correlatedwith a geofence database to determine the relevance of the anomalouscondition based upon whether other vehicles are located inside thegeofence. The geofence database may be stored, for example, in asuitable portion of computing device 300 (e.g., data storage 360) orretrieved via communications with one or more external computingdevices. To provide another illustrative example, a computing device 300may be implemented as an external computing device. The externalcomputing device may determine, from telematics data and geographiclocation data received from a first computing device 300, that a firstvehicle is located on a highway at a certain geographic location. Theexternal computing device may calculate a geofence having a shapesubstantially matching the road upon which the first vehicle istravelling.

The geofence may be calculated as having any suitable shape such thatthe appropriate vehicles are notified of the detected anomalouscondition. For example, the geofence shape may follow the contours ofthe road and extend ahead of the first vehicle and behind the firstvehicle some threshold distances, which may be the same or differentthan one another. To provide another example, the geofence shape mayinclude other arterial roads that feed into the road upon which thefirst vehicle is travelling, roads anticipated to be impacted by theanomalous condition, etc.

In some aspects, the geofence may be adjusted or modified based upon achange in the location of computing device 300. This change may betriggered using any suitable data indicative of potentially increasingroad densities, such as changes in population density data associatedwith the geographic location of the computing device 300, changes in atype of road upon which computing device 300 is determined to betravelling, etc.

For example, a first computing device 300 may be implemented as a mobilecomputing device and associated with a first vehicle, while a secondcomputing device 300 may be implemented as an external computing device.The external computing device may calculate an initial geofence as athreshold distance radius centered about the first vehicle's location.The geographic location data corresponding to the first vehicle'slocation may have associated population density data that is correlatedwith locally stored data or data retrieved by the external computingdevice. When the population density data surpasses a threshold densityvalue, the shape of the geofence may be adjusted from the radiuscentered about the first vehicle's location to include only the roadupon which the first vehicle is travelling In this way, computing device300 may prevent false alert notifications from being sent to othervehicles travelling in close proximity to the first vehicle, but onnearby roads unaffected by the detected anomalous condition.

To provide another illustrative example, as previously discussed, one ormore cameras integrated as part of sensor array 326 may store imageand/or video data from a vantage point within a vehicle in which mobilecomputing device 300 is mounted to act as a dashboard camera. Inaccordance with such aspects, anomalous condition detection routine 358may include instructions, that when executed by controller 340,facilitate the analysis of the image and/or video data to detect one ormore anomalous conditions that may pose an immediate threat, hazard,and/or inconvenience to the driver and/or other drivers in the vicinity.These anomalous objects may also be identified as a traffic event, aspreviously discussed.

In various aspects, any suitable type of object recognition and/or imagerecognition analysis may be performed upon captured image data to detectobjects in the path of the vehicle, such as animals, pedestrians, othervehicles, potholes, etc. Furthermore, the captured mage data may beanalyzed to identify other anomalous traffic conditions, events, etc.,such as vehicle conditions, traffic, congestion, road construction,weather conditions, etc.

Again, upon detecting an anomalous object, computing device 300 mayperform various corrective or preventive actions, such as generating,providing and/or displaying an audible alert, visual alert and/orrecommendation via display 316 and/or speaker/microphone 322.Additionally or alternatively, the corrective or preventive actions mayinclude the generation, calculation, and/or display of an alternateroute that avoids the location of the anomalous object, which is furtherdiscussed below. Because computing device 300 may be installed in avehicle driven by an insured driver, these corrective actions may bedirected to the insured driver in such instances. Thus, the correctiveor preventive actions performed by mobile computing device 300 mayalleviate or eliminate the risk of vehicle collisions or other damage toan insured vehicle or an insured driver.

Additionally or alternatively, mobile computing device 300 may, upondetecting an anomaly, broadcast one or more signals via communicationunit 330, which are received directly or indirectly by other mobilecomputing devices. Again, these other mobile computing devices may thengenerate alert notifications locally when close to the geographiclocation of mobile computing device 300 where the signal wasbroadcasted. Aspects in which the detected anomalous condition is sharedin this manner may be particularly useful when the identified anomaly islikely to threaten other drivers using the same road, such as potholesor objects blocking the roadway, for example.

The data transmitted via communication unit 330 may identify the type ofanomaly, the location of the anomaly, a description of the anomaly, etc.For example, once an anomaly is detected, a data transmission mayinclude a notification that identifies the type of abnormal condition orthe extent of the abnormal condition by a length of time over which theanomaly has been observed as a result of the analysis of the capturedimage data, which may be indicated, for example, using timestamps or anyother suitable indicator.

To provide another example, the transmission may include a notificationthat identifies the size or area impacted by the detected abnormalcondition. That is, the notification may include an identifier that notonly indicates the location of the detected anomaly, but an anticipatedarea of impact for other vehicles. The area of impact may be calculated,for example, based upon the type of anomaly and/or the severity of theanomaly that is detected. For example, the detection of aweather-related anomaly may result in an impact area being generatedthat is proportional to the severity of the weather (e.g., based uponwind speed, temperature, the presence of precipitation, etc.).

The inclusion of details regarding the type and severity of anidentified anomalous condition have been described above with referenceto anomalous conditions identified though the analysis of captured magedata. However, this information may be included with any telematics dataand/or notification transmission. For example, if the telematics dataindicates that the speed of the vehicle is less than a threshold vehiclespeed over a threshold duration of time, a generated notification mayinclude information such as the overall time and/or distance that theoriginating vehicle has (or still is) experiencing these delays.

In this way, any device provided herein configured to receive andanalyze telematics data (e.g., computing device 300, smart vehiclecontrol system 500, remote server 600, and/or smart infrastructurecomponent 700) may analyze the telematics data and/or other dataincluded in a telematics data transmission to estimate or determine theactual geographical or temporal scope of a travel event (e.g., anabnormal condition).

Additionally or alternatively, software routines 352 may include a routecalculation routine 359. In one aspect, controller 340 may executeinstructions stored in route calculation routine 359 to generate,calculate, and/or display travel routes, which may provide navigationalguidance to a driver. For example, data storage 360 may store map and/orcartographic data (or this data may be received via communication unit330 from an external computing device) to facilitate route mapping.

Furthermore, controller 340 may execute instructions stored in routecalculation routine 359 to facilitate additional or alternate correctiveor preventive actions when an anomaly is identified. For example,controller 340 may execute instructions stored in route calculationroutine 359 to facilitate the calculation of an alternate travel routethat avoids the location of the identified anomaly or an area associatedwith the anomaly (e.g., a radius, road, a geofence boundary, etc.),which may be displayed via display 316, for example.

Additionally or alternatively, controller 340 may execute instructionsstored in route calculation routine 359 to facilitate the receipt of analternate route (e.g., via one or more external computing devices, avehicle in which mobile computing device 300 is located, smartinfrastructure components, etc.) that avoids the location of theidentified anomaly. In an aspect, the alternative route may function todynamically re-route an insured vehicle while moving to avoid anlocation or area associated with an identified anomaly.

Although FIG. 3 depicts controller 340 as including one program memory302, one MP 306, and one RAM 308, controller 340 may include anysuitable number of program memory 302, MP 306, and RAM 308. Furthermore,although FIG. 3 depicts controller 340 as having a single I/O interface310, controller 340 may include any suitable number and/or types of I/Ointerfaces 310. In various aspects, controller 340 may implement RAM(s)308 and program memories 302 as any suitable type of memory, such asnon-transitory computer readable memories, semiconductor memories,magnetically readable memories, and/or optically readable memories, forexample.

Exemplary Screenshots of an Alert Notification Application

FIG. 4A illustrates an example mobile computing device home screen 400in accordance with an exemplary aspect of the present disclosure. Invarious aspects, home screen 400 is displayed on a mobile computingdevice, such as mobile computing device 110 or mobile computing devices204.1-204.2, as shown in FIGS. 1 and 2, respectively. In accordance withsuch aspects, home screen 400 may be displayed as part of a devicedisplay, such as display 316, for example, as shown in FIG. 3.

Home screen 400 may be displayed as a default screen on a mobilecomputing device. In one embodiment, home screen 400 may facilitate alock screen of a mobile computing device. Lock screens may be typicallydisplayed when a user locks the mobile computing device to enter a lockscreen mode (e.g., by pressing a physical button). Additionally oralternatively, the mobile computing device may revert to the lock screenwhen inactive for a threshold period of time. The lock screen prevents auser from using a portion of the mobile computing device functionality.For example, a lock screen might prevent a mobile computing device in auser's pocket from accidentally sending SMS messages or phone calls.

Although lock screens typically limit the functionality of the devicewhen enabled, it may be desirable for certain applications to provide auser with some functionality via the lock screen. For example, if themobile computing device is used to play music, a lock screen overlaycould allow a user to change tracks, pause a track, or adjust the volumelevel without unlocking the phone. In accordance with some aspects,alert notification 402 may be displayed as part of a home screen and/orlock screen of a mobile computing device, as shown in FIG. 4A.

Although alert notification 402 may be displayed as part of home screen400, other aspects include alert notification 402 being displayed aspart of a notification system separate from home screen 400. Forexample, some mobile phone operating systems (e.g., the Android OS)implement a universal “pull-down” notification system where ah incomingnotifications are displayed. In these notification systems, newnotifications are initially previewed in a notification bar at the topof the phone display, and a user may pull down the notification bar(e.g., by using a swiping gesture) to access the details of any receivednotifications. In one aspect, alert notification 402 may be displayed aspart of a notification bar type notification.

As previously discussed with reference to FIG. 3, a device running thealert notification application may be configured to determine whether ananomalous condition has been detected and/or to receive alertnotifications sent by other devices that have done so. In accordancewith such aspects, alert notification 402 is a block diagramrepresentation of what may be generated upon detection of an anomalouscondition and/or receiving an indication that an anomalous condition hasbeen detected. Alert notification 402 may be implemented as any suitablegraphic, label, text, description, etc., to convey this to a user. Inone embodiment, alert notification 402 may be interactive and mayfacilitate a user selection via an appropriate gesture (e.g., swiping,tapping, etc.).

FIG. 4B illustrates an example mobile computing device applicationscreen 450 in accordance with an exemplary aspect of the presentdisclosure. In various aspects, application screen 450 may be displayedon a mobile computing device, such as mobile computing device 110 ormobile computing devices 204.1-204.2, as shown in FIGS. 1 and 2,respectively. In accordance with such aspects, application screen 450may be displayed as part of a device display, such as display 316, forexample, as shown in FIG. 3.

In one aspect, application screen 450 may be displayed upon a userselecting alert notification 402 from home screen 400. Applicationscreen 450 may include an alert description 452 and an alert location454. Alert description 452 is a block diagram representation of one ormore descriptions of the alerts related to the detected anomalouscondition. Alert description 452 may be implemented as any suitablegraphic, label, text, description, etc., to convey this to a user. Forexample, alert description 452 may include a text description such as“slow traffic ahead,” “traffic at standstill ahead,” “unpaved roadahead,” “potential icy conditions ahead,” “pulled over vehicle ahead,”etc.

Alert location 454 is a block diagram representation of one or moredescriptions of the location of the anomalous condition. Alert location454 may be implemented as any suitable graphic, label, text,description, etc., to convey this to a user. For example, alert location454 may include a directional compass indicating a direction towards theanomalous condition from the mobile computing device displayingapplication screen 450. To provide additional examples, alert location454 may include a distance to the anomalous condition, a map overlaidwith the location of the mobile computing device displaying applicationscreen 450 to indicate the position of the mobile computing device inrelation to the anomalous condition, the threshold distances and/orgeofences used to determine the relevance of the anomalous condition,etc.

Exemplary Smart Vehicle Control System

FIG. 5 illustrates a block diagram of an exemplary smart vehicle controlsystem 500 in accordance with an exemplary aspect of the presentdisclosure. In the present aspect, smart vehicle control system 500 maybe implemented as any suitable computing device, such as a computingdevice that is integrated as part of a smart vehicle to facilitateautonomous driving and/or other smart driving functions. For example,smart vehicle control system may be integrated as part of one or morevehicles 201.1-202.N, as shown in FIG. 2, to provide these vehicles withsuch functionality. Smart driving functions may include, for example,the generation, receipt, collection, storage, and/or transmission oftelematics data or other data, such as data previously discussed abovewith reference to on board computer 114 (as shown in FIG. 1) mobilecomputing devices 204.1-204.N, and/or vehicles 202.1-202.N (as shown inFIG. 2), for example.

Smart vehicle control system 500 may include a sensor array 526, acommunication unit 530, a smart vehicle controller 540, one or morevehicle sensors 545, and/or a driving control system 550, one or more ofwhich may be configured to communicate with one another to receive datafrom, and send data to, one another. Smart vehicle control system 500may include additional, less, or alternate functionality, including thatdiscussed elsewhere herein, and/or discussed with reference to mobiledevices, remote servers, and/or smart infrastructure.

In an aspect, sensor array 526, communication unit 530, and smartvehicle controller 540 may have a similar architecture, implementation,and/or perform similar functions as sensor array 326, communication unit330, and controller 340, respectively, as previously discussed abovewith reference to FIG. 3. Therefore, only differences between sensorarray 526, communication unit 530, and smart vehicle controller 540, asshown in FIG. 5, and sensor array 326, communication unit 330, andcontroller 340, as shown in FIG. 3, will be further discussed herein.

For instance, it will be appreciated that some differences betweensensor array 526, communication unit 530, and smart vehicle controller540, as shown in FIG. 5, and sensor array 326, communication unit 330,and controller 340, as shown in FIG. 3, respectively, may be due todifferences between applications and design requirements of mobiledevice s and vehicles. For example, smart vehicle controller 540 mayinclude one or more microprocessors, program memory, RAM, 1/Ointerfaces, etc. However, smart vehicle controller 540 may includefaster microprocessors, additional memory, faster memory controllers,etc., than that of controller 340 to account for the additionalprocessing and speed requirements associated with the higher processingfunctions of vehicles, particularly smart vehicles. To provide anotherexample, smart vehicle controller 540 may include one or more processorsspecifically designed for adaptive vision processing at high speedsand/or utilizing parallel processing techniques to facilitate autonomousor semi-autonomous driving.

Likewise, sensor array 526 may have additional or alternative sensorsand/or meters than sensor array 326. Sensor array 526 may additionallyor alternatively include any suitable number and/or type of sensorsand/or meters to facilitate autonomous or semi-autonomous drivingExamples of sensors included in sensor array 526 may include, forexample, radar systems configured to operate at any suitable number orrange of wavelengths (e.g., millimeter-wavelengths), LiDAR, ultrasonicsensors, etc.

Vehicle sensors 545 may include, for example, any suitable number and/ortype of sensors and/or meters integrated as part of the vehicle in whichsmart vehicle control system 500 is installed or otherwise implemented.For example, vehicle sensors 545 may generate one or more sensor metricsor other data that is part of the telematics data that is stored,collected, and/or broadcasted from smart vehicle control system 500(e.g., via communication unit 530).

In some aspects, vehicle sensors 545 may sample sensor metrics or otherinformation that is included as part of the telematics data, asdiscussed elsewhere herein, while sensor array 526 may be implemented asone or more sensors associated with autonomous driving functions. Thus,in aspects in which smart vehicle control system 500 is implemented aspart of a non-autonomous vehicle, vehicle sensors 545 and sensor array526 may be implemented as a single sensor array.

Communication unit 530 may be configured to transmit and/or receive anysuitable type of data. To accomplish this, communication unit 530 may beimplemented with any suitable number and/or type of hardware componentssuch as, for example, one or more transceivers, receivers, transmitters,antennas, ports, etc.

Smart vehicle controller 540 may be configured to operate in conjunctionwith one or more of vehicle sensors 545, communication unit 530, drivingcontrol system 550, and/or sensor array 526 to process and/or analyzedata, to store data to one or more memory units associated with smartvehicle controller 540, to retrieve data from one or more memory unitsassociated with smart vehicle controller 540, and/or to perform one ormore functions of the various aspects as described herein.

For example, smart vehicle controller 540 and communication unit 530 mayfacilitate receiving data from and/or sending data to one or moredevices, such as one or more mobile computing devices, one or morevehicles, one or more infrastructure components, etc. To facilitate thisfunctionality, smart vehicle controller 540 may be coupled via one ormore wired and/or wireless interconnections to one or more othercomponents of smart vehicle control system 500, such as via any suitablenumber of data and/or address buses, for example. These interconnectionsare not shown in FIG. 5 for purposes of brevity.

In one aspect, communication unit 530 may be configured to transmittelematics data and/or other data. This data may include, for example,one or more sensor metrics, alert notifications, and/or othertelematics-data related messages (e.g., the extent, severity, type,and/or the geographic location of a traffic event or another anomalouscondition that has been detected or received). To provide additionalexamples, the data may include a location of smart vehicle controlsystem 500 or other information generated by vehicle sensors 545 and/orsensor array 526, which may be received by other mobile devices, othersmart vehicles, smart infrastructure, and/or external computing devices,as discussed elsewhere herein.

Additionally or alternatively, communication unit 530 may be configuredto receive any suitable type of data, such as data generated and/orcollected by other smart vehicle control systems 500, as discussed abovewith respect to data transmissions. For example, communication unit 530may be configured to receive data transmitted by other mobile devices,other smart vehicles, smart infrastructure, and/or external computingdevices, as discussed elsewhere herein.

Again, the telematics data or a telematics data transmission (which mayinclude telematics data and any other suitable type of data, asdiscussed above) may include information that identifies the nature,severity, and/or area of impact of a travel event or other anomalouscondition. This information may thus identify the travel event or otheranomalous condition in which the computing device or vehicle hasencountered or is presently encountering. Smart vehicle control system500 may then use such information to identify the travel event at thatlocation and/or to take or direct corrective or preventive action tofacilitate safer vehicle travel for the moving vehicle in whichcomputing device 300 is located. For example, smart vehicle controlsystem 500 may generate, display, and/or provide an alert for the driverof the moving vehicle in which smart vehicle control system 500 islocated, which is further discussed below.

In one aspect, smart vehicle controller 540 may work in conjunction withcommunication unit 530 to periodically listen for and/or to periodicallybroadcast telematics data. For example, smart vehicle controller 540 mayperiodically listen for a broadcast containing telematics data generatedand transmitted from other mobile computing devices, vehicles, externalcomputing devices, and/or smart infrastructure components. Upondetecting a broadcast, smart vehicle controller 540 may download thebroadcast to a suitable portion of one or more of its memory units andanalyze the telematics data contained therein for potential trafficevents, travel events, alerts, messages, etc. Such aspects may beparticularly useful, for example, to save power, as continuous listeningis not necessary (although possible) but instead may be performed, forexample, in accordance with a particular timing schedule.

To provide another example, smart vehicle controller 540 may causecommunication unit 530 to periodically broadcast telematics data, whichmay be received by other mobile computing devices, vehicles, externalcomputing devices, and/or infrastructure components. To provide anillustrative example, the telematics data may be sampled, updated,and/or broadcasted in accordance with a periodically recurring scheduleor sampling rate (e.g., five times per second, every second, once every5 seconds, once every ten seconds, etc.).

When transmitting telematics data, smart vehicle controller 540 may beconfigured to format the sensor metrics and/or other informationgenerated, collected, and/or measured by vehicle sensors 545 and/orsensor array 526 into a telematics data broadcast, determine whether thetelematics data should be updated, and/or broadcast the telematics data.Additionally or alternatively, smart vehicle controller 540 may beconfigured to analyze the telematics data to identify one or moreanomalous conditions (e.g. travel events, traffic events), and/oralerts, to generate one or more messages associated with the telematicsdata and/or detailing the type and/or extent of an identified anomalyand/or alert, etc.

Furthermore, smart vehicle controller 540 may be configured to broadcastor otherwise direct a transmission of the message via data transmissionand/or wireless communication (e.g., via communication unit 530) toanother computing device (such as a mobile device, another vehicle, aremote server, smart infrastructure, etc.). As further discussed herein,devices receiving the telematics data and/or message may utilize thetelematics data to perform various functions, issue alerts to drivers,etc. In this way, the telematics data and/or messages transmitted bysmart vehicle control system 500 may facilitate safer travel for anothervehicle and/or another driver.

As discussed above with reference to FIG. 3, the identified anomaly(e.g., a travel event, traffic event, etc.) may be based upon (and/ordetermined from telematics data that reveals) abnormal trafficconditions, congestion, road construction, and/or weather conditions,etc., and may include any suitable condition that indicates a deviationfrom normal traffic patterns or otherwise poses a potential hazard orinconvenience to other drivers.

In various aspects, the identified anomaly may be detected by smartvehicle controller 540 based upon an analysis of locally generated orcollected telematics data, telematics data received from anothercomputing device via communication unit 530, an analysis of datatransmitted with and/or included as part of a telematics data broadcastor transmission, and/or an analysis of one or more receivedtelematics-related messages (e.g., alert notifications).

Similar to other devices described above (e.g., computing device 300),when receiving telematics data, smart vehicle controller 540 may beconfigured to perform various functions such as issuing alerts todrivers when the telematics data contains a warning message and/oridentifying an anomalous condition by analyzing the received telematicsdata.

For example, smart vehicle controller 540 may execute instructionsstored in one or more of its associated memory units to determine oridentify whether a travel event exists associated with telematics datareceived from an originating device or vehicle, a GPS location or otherlocation of the travel event, whether the telematics data includes amessage indicating the existence of the travel event, an estimated oractual geographical or temporal scope of the travel event from ananalysis of telematics data, etc. The techniques to identify thisinformation may be substantially similar to or identical as thosediscussed above, for example, with respect to computing device 300 aswell as elsewhere herein.

In other words, similar to computing device 300, smart vehiclecontroller 540 may analyze the telematics data itself and/or anysuitable portion of the transmission in which the telematics data issent to attempt to identify an alert, indication, and/or messageregarding a travel event or other anomalous condition that has alreadybeen identified by another device. For example, the telematics data (orother data sent with the telematics data as part of a data transmission)may include a message or other information indicating a type ofanomalous condition or travel event, when it was detected, and itslocation.

Driving control system 550 may be implemented with any suitable numberand/or type of driving controllers to control the direction, movement,and/or speed of the vehicle in which smart vehicle control system 500 isinstalled. For example, driving control system 550 may include variousdrive-by-wire interfaces to facilitate controlling the speed of thevehicle and to turn the vehicle without user input. To provide anadditional example, driving control system may include various brakingcontrollers and/or transmission controllers to slow the vehicle and toshift the vehicle into different gears.

In accordance with one aspect, smart vehicle controller 540 maycommunicate with one or more components of driving control system 550 inresponse to telematics data, information, and/or messages received viacommunication unit 530. For example, if the telematics data indicates aroad hazard at a certain location and/or in a certain road lane, thensmart vehicle controller 540 may issue one or more commands to drivingcontrol system 550 to steer the vehicle into a clear lane, thus avoidingthe road hazard.

Driving control system 550 may include different types of feedbackcomponents and/or control systems based upon the type of vehicle inwhich smart vehicle control system 500 is implemented or installed. Forexample, driving control system 550 may include various interfacesand/or control systems to facilitate autonomous driving in conjunctionwith smart vehicle controller 540. But if smart vehicle control system500 is implemented in a non-autonomous vehicle (or is implemented aspart of an autonomous vehicle but being operated in a non-autonomousmode of operation), driving control system may work in conjunction withsmart vehicle controller 540 to receive one or more signals and/or dataassociated with traditional driving functions performed by a driver ofthe vehicle (e.g., manual acceleration, steering, braking, etc.).

Regardless of the type of vehicle in which smart vehicle control system500 is implemented, smart vehicle controller 500 may work in conjunctionwith driving control system 550 to support any suitable number and/ortype of driver feedback. To provide this feedback, driving controlsystem 550 may include any suitable number and/or type of displays, userinterfaces, speakers, buzzers, etc.

For example, driving control system 550 may include various feedbackcomponents to provide visual and/or auditory feedback regarding theoperation of the vehicle and/or information regarding anomalousconditions, alerts, warnings, recommendations, etc., which may be basedupon an analysis of telematics data. Again, the telematics data may bereceived from another computing device (e.g., via communication unit530) and/or generated and analyzed locally at smart vehicle controlsystem 500.

To provide another example, smart vehicle controller 540 may include oneor more memory units configured to store computer readable instructions,cartographic and/or map data, vehicle navigation information, virtualroad maps, etc. In various aspects, the one or more memory unitsassociated with smart vehicle controller 540 may be implemented as anon-transitory tangible computer readable media configured to storecomputer-readable instructions, that when executed by smart vehiclecontroller 540, cause smart vehicle controller 540 to perform variousacts.

In response to user input received via a user interface implemented bydriving control system 550, smart vehicle controller 540 may generate,calculate, and/or display travel routes, which may provide navigationalguidance to a driver. Furthermore, smart vehicle controller 540 mayperform functions associated with the determination of whether anidentified anomaly, which has been determined from an analysis ofreceived telematics data from another device, is relevant to the vehiclein which smart vehicle control system 500 is implemented.

This determination of relevance may be made, for example, by comparing alocation (e.g., geographic coordinates included in a telematics datatransmission) to the current location of smart vehicle control system500 to determine whether the locations are within a threshold distanceof one another. These locations may include, for example, geographiclocations defined by GPS coordinates or any other suitable techniquesthat may adequately identify the location of smart vehicle controlsystem 500 and another vehicle, another device, another smart vehiclecontrol system, smart infrastructure, etc.

The determination may also be made, for example, when the identifiedanomaly or other abnormal condition is located along a current travelroute (e.g., ahead by some threshold distance in a direction of travelon the same road in which the vehicle in which smart vehicle controlsystem 500 is implemented is moving). If so, aspects include smartvehicle controller 540 automatically performing various preventativeand/or corrective actions based upon how the relevance of the identifiedanomaly is determined.

For example, smart vehicle controller 540 may issue a visual and/oraudible alert via driving control system 550, issue a visual and/oraudible recommendation for the driver of the vehicle associated withsmart vehicle control system 500 via driving control system 550 (e.g., arecommendation to take an alternate route, change lanes, slow down,engage all-wheel drive, etc.), calculate and/or display an alternatetravel route via driving control system 550 that avoids the location ofthe identified event, etc.

To provide additional examples, when smart vehicle control system 500 isimplemented as part of a vehicle capable of autonomous driving, thecorrective or preventive action may include automatically orsemi-automatically re-routing the vehicle. In other words, smart vehiclecontrol system 500 may not only calculate and/or receive an alternateroute that avoids the location of the identified event, but activelyre-route and drive the vehicle to avoid a location or area associatedwith the identified event.

In some aspects, the preventative and/or corrective action may be issuedonly when it is determined that an identified anomaly is relevant, andis otherwise not issued. For example, aspects include an identifiedanomaly that is not along a current route for the vehicle in which smartvehicle control system 500 is implemented not causing an alarm to besounded and/or the route to be adjusted, even if the location of theanomaly is otherwise nearby. In this way, the preventive or correctiveaction may alleviate or avoid a negative impact of the abnormal travelcondition on the driver and/or the vehicle in which smart vehiclecontrol system 500 is implemented to facilitate safer or more efficientvehicle travel without unnecessarily issuing alerts.

As discussed above with reference to FIG. 3, various aspects include thedata generated, collected, and/or received by smart vehicle controlsystem 500 being leveraged to calculate a usage amount in which a userutilizes the telematics data-based risk mitigation or preventionfunctionality provided by smart vehicle control system 500 whiledriving. This functionality may include, for example, any of thetelematics data collection, generation, transmission, reception, and/orcorrective actions described throughout this disclosure. Similarly,smart vehicle controller 540 may calculate various usage metricsregarding a driver utilizing these functions while driving the vehicle(or being in an autonomous vehicle without necessarily driving it) inwhich smart vehicle control system 500 is implemented.

Again, as discussed above, the usage amount may be time-based ormileage-based. As discussed above, this usage data may be sent to aninsurer or other third party via a telematics data transmission or aseparate transmission and used to set and/or adjust an insurance policy,premium, or discount for the insured customer.

Exemplary Remote Server

FIG. 6 illustrates a block diagram of an exemplary remote server 600 inaccordance with an exemplary aspect of the present disclosure. Remoteserver 600 may be implemented as any suitable computing device. In oneaspect, remote server 600 may be an implementation of external computingdevice 206, for example, as shown in FIG. 2. In an aspect, remote server600 may include a processor 602, a communication unit 604, a display605, a user interface 606, and a memory 608. Remote server 600 mayinclude additional, fewer, or alternate components, including thosediscussed elsewhere herein.

Processor 602 may be implemented as any suitable type and/or number ofprocessors, such as a host processor of remote server 600, for example.To provide additional examples, processor 602 may be implemented as anapplication specific integrated circuit (ASIC), an embedded processor, acentral processing unit (CPU) associated with remote server 600, agraphical processing unit (GPU), etc.

Processor 602 may be configured to communicate with one or more ofcommunication unit 604, display 605, user interface 606, and/or memory608 via one or more wired and/or wireless interconnections, such as anysuitable number of data and/or address buses, for example. Theseinterconnections are not shown in FIG. 5 for purposes of brevity.

Processor 602 may be configured to operate in conjunction with one ormore of communication unit 604, display 605, user interface 606, and/ormemory 608 to process and/or analyze data, to store data to memory 608,to retrieve data from memory 608, and/or to perform one or moreinsurance-related and/or telematics data-based functions. For example,processor 602 and communication unit 604 may facilitate receiving datafrom and/or sending data to one or more devices, such as one or moremobile computing devices 204.1-204.N, one or more vehicles 202.1-202.N,one or more infrastructure components 208, etc.

Communication unit 604 may be configured to facilitate communicationsbetween remote server 600 and one or more other devices. For example, inaspects in which remote server 600 is an implementation of externalcomputing device 206, as shown in FIG. 2, communication unit 604 mayfacilitate communications between external computing device 206 and oneor more mobile computing devices 204.1-204.N, one or more vehicles202.1-202.N, one or more infrastructure components 208, etc.

In various aspects, remote server 600 may be configured to communicatewith these other devices in accordance with any suitable number and/ortype of communication protocols. Thus, communication unit 604 may beimplemented with any suitable hardware, firmware, and/or software tofacilitate the various aspects described herein. For example,communication unit 604 may be implemented with any suitable numberand/or type of hardware components such as, for example, one or moretransceivers, receivers, transmitters, antennas, ports, etc.

In some aspects, remote server 600 may function as a relay, receivingtelematics data and/or other data from one or more devices, processingthe data, and transmitting the data to other devices. In accordance withsuch aspects, communication unit 604 may be configured to receive a datatransmission or wireless communication containing or includingtelematics data, which may be generated and transmitted, for example,from a first mobile device (e.g., mobile computing device 204.1 orvehicle 202.1, as shown in FIG. 2). Again, as discussed throughout thisdisclosure, mobile computing device 204.1 and/or vehicle 202.1 may beassociated with a driver when appropriate (e.g., when vehicle 202.1 is anon-autonomous vehicle or an autonomous vehicle being operated in anon-autonomous fashion).

Continuing this example, once communication unit 604 receives thetelematics data and/or other data from mobile computing device 204.1 orvehicle 202.1, processor 702 may analyze the data, determine whether atravel event or anomalous condition exists, determine the location ofany identified travel events, and cause communication unit 604 totransmit a travel event-related data transmission or wirelesscommunication (e.g., a warning message, notification, and/or thetelematics data and/or other data) to another mobile computing device orvehicle (e.g., mobile computing device 204.2 or vehicle 202.2, as shownin FIG. 2). The techniques utilized by remote server 600 to identifytravel events may be similar to those previously explained withreference to computing device 300, and/or smart vehicle control system500, as shown in FIGS. 3 and 5, respectively.

Upon receiving the data transmission or wireless communication at thesecond mobile device or second vehicle (e.g., mobile computing device204.2 or vehicle 202.2) the mobile device or vehicle may use thetelematics data, notification, message, etc., to take corrective orpreventive action. In this way, remote server 600 may enable safervehicle travel for a second driver (or vehicle) based upon thetelematics data associated with a first driver (or vehicle).

Furthermore, because telematics data and/or a telematics datatransmission received by remote server 600 may include geographiclocation information and/or other information detailing the type oftravel event, the area of impact, severity, length of time over whichthe event has elapsed, etc., remote server 600 may also determine theGPS location or other location of the travel event and/an estimated oractual geographical or temporal scope of the travel event. Again, thetechniques to identify this information may be substantially similar toor identical as those discussed above, for example, with respect tocomputing device 300 and/or smart vehicle control system 500 as well aselsewhere herein.

Display 605 may be implemented as any suitable type of display and mayfacilitate user interaction with remote server 600 in conjunction withuser interface 606. For example, display 605 may be implemented as acapacitive touch screen display, a resistive touch screen display, etc.In various aspects, display 605 may be configured to work in conjunctionwith processor 602 and/or user interface 606 to display collectedtelematics data received from one or more mobile computing devicesand/or vehicles, to display the result of various insurance-relatedcalculations, to display the location of one or more mobile computingdevices and/or vehicles, to display insurance profile data and/or otherinformation associated with an insurance policy and/or an insuredcustomer, to provide a graphical user interface (GUI) to facilitate theviewing, adjustment, and/or accessing of insurance-related data, etc.

User-interface 606 may be implemented as any suitable device configuredto collect user input, such as a “soft” keyboard displayed on display605, a keyboard attached to remote server 600, an external keyboardcommunicating via a wired or a wireless connection (e.g., a BLUETOOTHkeyboard), an external mouse, etc.

In some aspects, remote server 600 may perform various tasksautomatically and without user intervention. For example, as discussedherein, remote server 600 may receive telematics data from variousdevices, process the telematics data, relay a telematics datatransmission, and/or perform various insurance-related calculationswithout user interaction with remote server 600. Thus, in accordancewith such aspects, display 605 and/or user interface 606 may beunnecessary. In other words, display 605 and/or user interface 606 maybe omitted or, if implemented by remote server 600, remain unused whilesuch automated tasks are performed.

In various aspects, memory 608 may be implemented as a non-transitorytangible computer readable media configured to store computer-readableinstructions, that when executed by processor 602, cause processor 602to perform various acts. Program memory 608 may store one or moremodules, which may be executed by processor 602 in conjunction with oneor more other hardware or software components of remote server 600 tofacilitate the execution of one or more functions related to the variousaspects, examples of which are further discussed below.

Data aggregation module 620 may include instructions to facilitatereceiving telematics data or other data from one or more devices, suchas one or more mobile computing devices 204.1-204.N, one or morevehicles 202.1-202.N, and/or one or more infrastructure components 208,for example, as shown in FIG. 2. Data aggregation module 620 may includeinstructions that, when executed by processor 602, enable processor 602to process data sent by one or more other devices, to identify a deviceand/or user associated with each device, and/or to store the telematicsdata in any suitable portion of memory 608 and/or in another suitablestorage device (which may be part of remote server 600 or anotherexternal computing device in communication with remote server 600).

For example, processor 602 may execute instructions stored in dataaggregation module 620 to receive broadcasted telematics datatransmissions from one or more mobile computing devices, to identify auser of each the mobile computing devices, and store this information ina manner such that each user may be correlated with each respectivemobile computing device. To provide an illustrative example, mobilecomputing device 204.1 may broadcast telematics data indicative of theoperation and/or motion of vehicle 202.1, which is received by remoteserver 600 via communication unit 604. Additionally or alternatively,mobile computing device 204.1 may transmit various messages, warnings,notifications, location data, a username associated with an insureddriver using mobile computing device 204.1, usage data associated withwhen the Telematics App is executed on mobile computing device 204.1,data indicative of a detected anomalous travel event, condition, orother hazard at the location associated with mobile computing device204.1 and/or vehicle 202.1, etc.

In one aspect, processor 602 may work in conjunction with communicationunit 604 to periodically listen for and/or to periodically broadcasttelematics data. For example, processor 602 may periodically listen fora broadcast containing telematics data generated and transmitted fromother mobile computing devices, vehicles, external computing devices,and/or infrastructure components. Upon detecting a broadcast, processor602 may download the broadcast to a suitable portion of memory 608 andanalyze the telematics data contained therein for potential trafficevents, travel events, alerts, messages, etc. Such aspects may beparticularly useful, for example, to save power, as continuous listeningis not necessary (although possible) but instead may be performed, forexample, in accordance with a particular timing schedule.

To provide another example, processor 602 may cause communication unit604 to periodically broadcast telematics data, which may be received byother mobile computing devices, vehicles, external computing devices,and/or infrastructure components. To provide an illustrative example,the telematics data may be sampled, updated, and/or broadcasted inaccordance with a periodically recurring schedule or sampling rate(e.g., five times per second, every second, once every 5 seconds, onceevery ten seconds, etc.).

Aspects include remote server 600, via execution of instructions storedin data aggregation module 620 by processor 602, storing any suitabletype of data received from any suitable number and/or type of devices.This data may be stored in a manner such that a user associated witheach device (e.g., an insured driver), the device itself and thetelematics data or other data transmitted by the device (and the timewhen such data was transmitted) may all be identified and correlated toone another for additional processing, as further discussed below.

Data processing module 622 may include instructions that, when executedby processor 602, enable processor 602 to process data received byremote server 600 from one or more other devices, as discussed above andelsewhere herein. For example, processor 602 may execute instructionsstored in data processing module 622 to identify an insured customerassociated with a device (e.g., a mobile computing device or vehicletransmitting telematics data) and/or to determine whether the insuredcustomer has given consent to monitoring and/or tracking of time-basedor mileage-based usage of the Telematics App installed on the insurancecustomer's mobile device while the insurance customer is driving aninsured vehicle. When consent is verified, aspects include remote server600 analyzing the telematics data to calculate a time-based or amileage-based usage of the Telematics App, as previously discussed withreference to FIG. 3.

In the present aspect, the determination of whether an insured customerhas provided consent may be performed using any suitable number and/ortype of techniques. For example, the Telematics Application may includeinstructions that, as a condition to its installation, require aninsured customer to provide such consent. To provide another example,the insured customer's insurance profile may maintain an indication thatthis consent was provided, which may be accessed by remote server 600for verification.

Data processing module 622 may additionally or alternatively facilitateremote server 600 determining whether an insured customer associatedwith a mobile computing device and/or vehicle has a TelematicsApplication installed. For example, the data received from a mobilecomputing device may indicate the insurance customer's logon usernamebut, when correlated to data received from the mobile computing device,indicates a lack of telematics data transmissions.

To provide another example, upon installation of the telematicsapplication, the mobile computing device may communicate with remoteserver 600 via one or more application programming interfaces (APIs).Upon doing so, remote server 600 may use data transmitted in the APIcommunications (e.g., various flags, indicators, etc.) to determinewhether the insurance customer has installed the Telematics Applicationon her respective mobile computing device.

Insurer data access module 624 may include instructions to facilitateremote server 600 accessing, reading, storing and/or updating insurerdata. For example, as discussed above with reference to FIG. 3, aninsurer may maintain stored insurer profile data, which may include, forexample, insurance policy numbers, a description and/or listing ofinsured assets, vehicle identification numbers of insured vehicles,addresses of insured structures, contact information, premium rates, oneor more qualifying discounts, etc.

In various aspects, some portions of the insurer data may be secured bythe insurer as proprietary information, while other aspects of theinsurer data may be made available to authorized users via the Internet(e.g., those providing the correct logon credentials). Processor 602 mayexecute instructions stored in insurer data access module 624 to allowparties access to insurer data in accordance with the appropriate levelof access established by the insurer.

In one aspect, processor 602 may execute instructions stored in insurerdata access module 624 to facilitate accessing this data and/ormanipulating this data. For example, an insured customer may beassociated with an insurance profile including an automotive insurancepolicy having a corresponding premium, which may be the result of theinsured customer qualifying for various discounts. As discussed abovewith reference to FIG. 3, the various discounts may be provided by aninsurer based upon the usage amount (e.g., time-based or mileage-based)whereby the insured customer uses the Telematics Application, whetherthe insured customer has the Telematics Application installed, etc. Inan aspect, processor 602 may execute instructions stored in insurer dataaccess module 624 to utilize an insured customer's logon credentials toaccess this data and/or to make this data available for variousinsurance-related calculations, as discussed below and elsewhere herein.

Policy calculation module 626 may include instructions to facilitateremote server 600 calculating insurance-related pricing related to oneor more insurance policies. This insurance-related pricing may be basedupon, for example, the telematics data and/or an insured customer'susage of a Telematics Application. In the event that processor 602, whenexecuting instructions stored in policy calculation module 626, resultsin a change in the stored insurer profile data, processor 602 mayadditionally execute instructions stored in insurer data access module624 to update the stored insurer profile data with updated insurancepricing. Additionally or alternatively, processor 602 may executeinstructions stored in insurer data access module 624 to update otherinsurer profile data such as discount information, telematics data,Telematics Application usage information, etc.

To provide an illustrative example, processor 602 may executeinstructions stored in policy calculation module 626 to analyzetelematics data received over some period of time for an identifiedinsured customer. Remote server 600 may analyze the telematics datausing any suitable number and/or type of analysis to appropriatelyallocate risk associated with the insurance customer based upon thetelematics data (e.g., whether the insured customer regularly drives inexcess of the posted speed limit, drives recklessly, drives or parks inareas associated with high crime rates and/or high accident rates,etc.). Based upon the allocated risk, processor 602 may executeinstructions stored in policy calculation module 626 to calculate asuitable insurance premium, determine whether the insured customer haslost one or more discounts, is eligible for additional safe-drivingdiscounts, etc.

To provide another illustrative example, processor 602 may executeinstructions stored in policy calculation module 626 to calculate,update, and/or adjust an insurance policy premium or discount based uponthe time-based usage or mileage-based usage of the TelematicsApplication by the insurance customer's mobile device. In other words,remote server 600 may calculate a usage amount associated with theinsured customer's usage of the Telematics Application while thecustomer drove an insured vehicle, and update or adjust the customer'sinsurance policy premium to provide a reduced cost for increased usageof the Telematics application. In this way, the use of the TelematicsApplication may facilitate rewarding risk-averse drivers and encourageusage of risk-mitigation or prevention technology.

Exemplary Smart Infrastructure Component

FIG. 7 illustrates a block diagram of an exemplary smart infrastructurecomponent 700 in accordance with an exemplary aspect of the presentdisclosure. In the present aspect, smart infrastructure component 700may be implemented as any suitable computing device, such as a computingdevice that is integrated as part of a smart roadside infrastructure,billboard, sign, railroad crossing lights, etc., to facilitate thereceipt and/or transmission of telematics data and/or other data.Additionally or alternatively, smart infrastructure component 700 mayfacilitate various functions to warn and/or notify other drivers and/orvehicles based upon received telematics data and/or data included intelematics data transmissions. In one aspect, smart infrastructurecomponent 700 may be integrated as part of infrastructure component 208,as shown in FIG. 2.

In one aspect, smart infrastructure component 700 may include aprocessor 702, a communication unit 704, a notification system 705, anda memory 708, one or more of which may be configured to communicate withone another to receive data from, and/or send data to, one another.Smart infrastructure component 700 may include additional, fewer, oralternate components, including those discussed elsewhere herein.Furthermore, smart infrastructure component 700 may include additional,less, or alternate functionality, including that discussed elsewhereherein, and/or discussed with reference to mobile devices, remoteservers, and/or smart infrastructure.

In an aspect, processor 702, communication unit 704, notification system705, and memory 708 may have a similar architecture, implementation,and/or perform similar functions as processor 602, communication unit604, display 605, and memory 608, respectively, as previously discussedabove with reference to remote server 600, as shown in FIG. 6.Therefore, only differences between processor 702, communication unit704, notification system 705, and memory 708 (as shown in FIG. 7), andprocessor 602, communication unit 604, display 605, and memory 608 (asshown in FIG. 6), will be further discussed herein.

For instance, it will be appreciated that some differences between thecomponents of smart infrastructure component 700 and remote server 600may be due to differences between applications and design requirementsof infrastructure components and servers. For example, communicationunit 704 may be configured to receive data from less devices than remoteserver 600 and, as a result, communication unit 704 may be configured toreceive and/or transmit data using less bandwidth than communicationunit 604 of remote server 600. To provide another example, processor 702may be configured to perform less complex tasks when integrated as partof smart infrastructure component 700 as opposed to processor 602, whichmay be implemented as part of remote server 600. Thus, althoughprocessor 702 may be configured to facilitate any suitable functions ofthe aspects described herein with reference to smart infrastructurecomponent 700, processor 702 may do so with lower performance comparedto processor 602.

Processor 702 may be configured to communicate with one or more ofcommunication unit 604, display 605, user interface 606, and/or memory608 via one or more wired and/or wireless interconnections, such as anysuitable number of data and/or address buses, for example. Theseinterconnections are not shown in FIG. 5 for purposes of brevity.Furthermore, processor 702 may be configured to operate in conjunctionwith one or more of communication unit 704, notification system 705, andmemory 708 to process and/or analyze data, to store data to memory 708,to retrieve data from memory 708, and/or to perform one or moretelematics data-based functions. For example, processor 702 andcommunication unit 704 may facilitate receiving telematics data fromand/or sending telematics data to one or more devices, such as one ormore mobile computing devices, one or more vehicles, one or more remoteservers, etc.

Communication unit 704 may be configured to facilitate communicationsbetween smart infrastructure component 700 and one or more otherdevices. For example, in aspects in which smart infrastructure component700 is an implementation of infrastructure component 208, as shown inFIG. 2, communication unit 704 may facilitate communications betweeninfrastructure component 208 and one or more mobile computing devices204.1-204.N, one or more vehicles 202.1-202.N, one or more remoteservers 206, etc.

In various aspects, smart infrastructure component 700 may be configuredto communicate with these other devices in accordance with any suitablenumber and/or type of communication protocols. Thus, in various aspects,communication unit 704 may be implemented with any suitable hardware,firmware, and/or software to facilitate the various aspects describedherein. For example, communication unit 704 may be implemented with anysuitable number and/or type of hardware components such as, for example,one or more transceivers, receivers, transmitters, antennas, ports, etc.

Similar to other devices described herein (e.g., computing device 300,smart vehicle control system 500, etc.), in some aspects, smartinfrastructure component 700 may function as a relay, receivingtelematics data and/or other data from one or more devices, processingand/or analyzing the data, determining whether a travel event oranomalous condition exists, determining the location of any identifiedtravel events, and causing communication nit 704 to transmit a travelevent-related data transmission or wireless communication (e.g., awarning message, notification, and/or the telematics data and/or otherdata) to another mobile computing device or vehicle (e.g., mobilecomputing device 204.2 or vehicle 202.2, as shown in FIG. 2). Thetechniques utilized by smart infrastructure component 700 to identifytravel events may be similar to those previously explained withreference to computing device 300, smart vehicle control system 500,and/or remote server 600, as shown in FIGS. 3, 5, and 6, respectively.These techniques are further discussed below.

Again, upon receiving the data transmission or wireless communication atthe second mobile device or second vehicle (e.g., mobile computingdevice 204.2 or vehicle 202.2) the mobile device or vehicle may use thetelematics data, notification, message, etc., to take corrective orpreventive action. In this way, smart infrastructure component 700 mayenable safer vehicle travel for a second driver (or vehicle) based uponthe telematics data associated with a first driver (or vehicle).

In one aspect, processor 702 may work in conjunction with communicationunit 704 to periodically listen for and/or to periodically broadcasttelematics data. For example, processor 702 may periodically listen fora broadcast containing telematics data generated and transmitted fromother mobile computing devices, vehicles, external computing devices,and/or infrastructure components. Upon detecting a broadcast, processor702 may download the broadcast to a suitable portion of memory 708 andanalyze the telematics data contained therein for potential trafficevents, travel events, alerts, messages, etc. Such aspects may beparticularly useful, for example, to save power, as continuous listeningis not necessary (although possible) but instead may be performed, forexample, in accordance with a particular timing schedule.

To provide another example, processor 702 may cause communication unit704 to periodically broadcast telematics data (e.g., when relayingdata), which may be received by other mobile computing devices,vehicles, external computing devices, and/or infrastructure components.To provide an illustrative example, the telematics data may be sampled,updated, and/or broadcasted in accordance with a periodically recurringschedule or sampling rate (e.g., five times per second, every second,once every 5 seconds, once every ten seconds, etc.).

In other aspects, smart infrastructure component 700 may function toprovide warning messages, notifications, or perform other preventive orcorrective actions, such as those discussed above with reference tocomputing device 300, smart vehicle control system 500, and/or remoteserver 600, for example, as shown in FIGS. 3, 5, and 6, respectively.Therefore, notification system 705 may be implemented with any suitablenumber and/or type of visual, auditory, and/or tactile system toeffectively warn other drivers and/or vehicles of identified anomalousconditions indicated by received telematics data and/or other data.

For example, if smart infrastructure component 700 is implemented as abillboard display, notification system 705 may include a displayconfigured to indicate the type of identified anomalous condition andits location (e.g., “left lane blocked 1 mile ahead,” “accident 2 milesahead—use alternate route,” etc.).

To provide another example, if smart infrastructure component 700 isimplemented as a road construction sign, then notification system 705may include one or more displays and/or warning signals to indicate thetype of an identified anomalous condition and its location.

To provide yet another example, if smart infrastructure component 700 isimplemented as a smart stop light, then notification system 705 mayinclude the traffic lights that change their timing patterns upondetecting heavy traffic flow in an attempt to alleviate the heavytraffic conditions.

Memory 708 may include a data processing module 720, a decision module722, and an execution module 724. Memory 708 may be configured as one ormore memory units configured to store computer readable instructions,cartographic and/or map data, vehicle navigation information, virtualroad maps, etc. In one aspect, memory 708 may be implemented as anon-transitory, computer readable media. Memory 708 may store one ormore modules, which may include computer readable instructions that,when executed by processor 702, facilitate the various aspects asdescribed herein.

For example, data processing module 720 may include instructions that,when executed by processor 702, cause smart infrastructure component 700to facilitate similar functions as those previously described withreference to the execution of data software applications 344 and/or oneor more software routines 352 by controller 340, as shown in FIG. 3.

Upon processor 702 executing instructions stored in data processingmodule 720, smart infrastructure component 700 may analyze receivedtelematics data to automatically identify or determine whether a travelevent exists. That is, smart infrastructure component 700 may determinewhether received telematics data (or a transmission including telematicsdata and/or other data) indicates the existence of a travel event usingsimilar techniques as described with reference to computing device 300,for example, and elsewhere herein.

Furthermore, because telematics data and/or a telematics datatransmission received by smart infrastructure component 700 may includegeographic location information and/or other information detailing thetype of travel event, the area of impact, severity, length of time overwhich the event has elapsed, etc., smart infrastructure component 700may also determine the GPS location or other location of the travelevent and/an estimated or actual geographical or temporal scope of thetravel event. Again, the techniques to identify this information may besubstantially similar to or identical as those discussed above, forexample, with respect to computing device 300, smart vehicle controlsystem 500, remote server 600, and/or elsewhere herein.

Based upon various conditions being satisfied, processor 702 may takedifferent types of actions once the travel event, location of the travelevent, and/or geographical or temporal extent of the travel event areidentified. To determine whether such conditions are met and/or whichactions to take, processor 702 may execute instructions stored indecision module 722 and execution module 724, respectively.

For example, as discussed above, in some aspects smart infrastructurecomponent 700 may relay received telematics data to other devices. Inother aspects, smart infrastructure component 700 may, once a travelevent is identified, relay various notifications, warnings, messages,etc., to one or more other devices. In still other aspects, smartinfrastructure component 700 may take corrective or preventive actionlocally in addition to or as an alternative to these other functions.

Therefore, decision module 722 may include instructions that, whenexecuted by processor 702, cause processor 702 to determine theappropriate action when a travel event is identified and/or whentelematics data or other data is received. This decision may be basedon, for example, the type of infrastructure component in which smartinfrastructure component 700 is implemented.

To provide an illustrative example, if smart infrastructure component700 is implemented as roadside construction sign, smart infrastructurecomponent 700 may be programmed or otherwise configured to displayalerts, warnings, and/or other messages of travel events as they areidentified. However, if smart infrastructure component 700 isimplemented as a smart infrastructure component lacking a display unit,then smart infrastructure component 700 may relay telematics data and/orother data and/or transmit messages notifying other devices of anidentified travel event without generating a local alert ornotification.

Additionally or alternatively, instructions stored in decision module722 may facilitate smart infrastructure component 700 determiningwhether an identified travel event is relevant to another device andtransmitting an alert notification (or the telematics data and/or otherdata) only when the travel event is relevant. For example, smartinfrastructure component 700 may utilize any suitable techniques todetermine relevance, as discussed above with reference to computingdevice 300 and elsewhere herein. Again, examples of relevant conditionsmay be based upon a geographic relationship between vehicles (identifiedfrom received telematics data transmissions) and/or route information(e.g., using a log of geographic location information from receivedtelematics data transmissions compared to map data, vehicle navigationinformation, virtual road maps, etc., stored in memory 708).

Furthermore, once a decision is made regarding the type of function toperform when a travel event is identified, the specific type of actionto execute may be determined via execution of instructions stored inexecution module 724 via processor 702. Similar to the instructionsstored in decision module 722, the instructions stored in executionmodule 724 may be customized or otherwise tailored to the type of devicein which smart infrastructure component 700 is implemented. For example,the instructions stored in execution module 724 may, when executed byprocessor 702, facilitate communication unit 702 relaying telematicsdata and/or other data, transmitting alert notifications, causing alocal notification to be displayed, cause processor 702 to control theexecution of various electromechanical functions (e.g., railroadcrossing gates to lower), etc.

Exemplary Smart Infrastructure or Remote Server

FIG. 8 illustrates an exemplary computer-implemented method 800 forreceiving, analyzing, and/or broadcasting telematics and/or other dataat or from an intermediary computing device to facilitate safer driving.Various devices are described herein to facilitate receiving telematicsdata and/or other data and analyzing this data to determine whethercorrective or preventive action should be taken. As described herein,telematics data may be generated locally at a particular originatingdevice (e.g., computing device 300, smart vehicle control system 500,remote server 600, smart infrastructure component 700, etc.) and/orreceived at a destination device from another device, which may includethe originating device or another intermediary device.

In other words, as discussed throughout the disclosure, any of thedevices described herein (e.g., computing device 300, smart vehiclecontrol system 500, remote server 600, smart infrastructure component700, etc.), which may be configured to receive telematics data and/orother data from an originating device, and/or analyze locally generatedtelematics data and/or data received from another device, mayadditionally be configured to relay telematics data and/or other data,messages, alert notifications, etc., to a destination device. When doingso, the relaying device may be referred to as an intermediary orintermediate device.

In the present aspect, the method 800 may be implemented by any suitablecomputing device (e.g., external computing device 206, as shown in FIG.2, computing device 300, as shown in FIG. 3, smart vehicle controlsystem 500, as shown in FIG. 5, remote server 600, as shown in FIG. 6,smart infrastructure component 700, as shown in FIG. 7, etc.). In oneaspect, the method 800 may be performed by one or more processors,applications, and/or routines. The method 800 may include additional,fewer, or alternate actions, including those discussed elsewhere herein.

The method 800 may start when one or more processors receive telematicsdata from an originating device (block 802). The originating device mayinclude, for example, a mobile device located in a vehicle, a smartvehicle control system integrated as part of a vehicle, a remote server,a smart infrastructure component, etc. Again, as discussed herein, thetelematics data may include, for example, any suitable type ofinformation that may be used to identify various anomalous conditions,events, inconveniences, hazards, etc. (block 802).

The method 800 may include one or more processors associated with adevice receiving the telematics data (e.g., an intermediary device)analyzing the telematics data to determine whether a travel event exists(block 804). Again, the travel event may include an event at anylocation, area, and/or region that may present a potential hazard and/oran inconvenience to other drivers, such as anomalous travel events,anomalous travel conditions, weather-related phenomena, extreme weatherconditions, high traffic conditions, traffic congestion, roadconstruction, etc., as well as other examples that are discussedthroughout the disclosure.

For example, method 800 may include one or more processors of theintermediary device analyzing the telematics data to determine whether anotification has been received indicating the existence of an abnormaltravel event at some location (block 804). In other words, theintermediary device may analyze the telematics data itself and/or anysuitable portion of the transmission in which the telematics data issent to attempt to identify an alert, indication, and/or messageregarding an abnormal travel event that has already been identified byan originating device (block 804).

The method 800 may include one or more processors of the intermediarydevice determining whether the telematics data (block 802) indicates atravel event that is relevant to or otherwise presents an issue to otherdrivers or vehicles (block 804). As discussed throughout the disclosure,this determination may be made in accordance with any suitabletechniques. For example, the intermediary device may compare thelocation of the travel event to the current location of a destinationvehicle. If these two locations are within a threshold or predetermineddistance of one another, the intermediary device may identify theabnormal travel event as one that may present an issue to thedestination vehicle or driver (block 804).

To provide another example, the location of the travel event may becompared to a route or road upon which the destination vehicle iscurrently traveling. If the location of the travel event is on the roador along the route on which the destination vehicle is travelling (e.g.,ahead and in a direction of travel on the same road in which the vehicleis moving), then the intermediary device may identify the travel eventas one that may present an issue to the destination vehicle or driver(block 804).

If the travel condition is relevant to the destination device orotherwise presents an issue, aspects include one or more processors ofthe to the intermediary device generating a warning message ornotification (block 806). Otherwise, method 800 may revert back tocontinuing to receive telematics data from the originating device (ormonitoring for such transmissions) (block 802).

The method 800 may include one or more processors of the intermediarydevice generating a warning message or notification (block 806). Again,the warning message or notification may be based upon the type ofintermediary device and/or the capabilities of the intermediary device.For example, if the intermediary device is implemented as a mobilecomputing device located in a vehicle or a smart vehicle control system,the warning message or notification may include generating an audible,visual, and/or tactile alert for the driver in which the intermediarydevice is located (block 806). To provide another example, if theintermediary device is implemented as a smart infrastructure component,then the warning message or notification may be a billboard displaymessage, a roadside construction sign message, etc. (block 806).

The method 800 may include one or more processors of the intermediarydevice transmitting the warning message or notification (block 808).This may include, for example, the intermediary device relaying thenotification and/or message using any suitable number and/or type ofcommunication protocols to a destination device (block 808). Uponreceiving the notification and/or message, the destination device maytake the appropriate preventive or corrective action (e.g., generatingan alternate route that avoids the location of the travel event,generating or determining an alert, re-routing a vehicle, etc.) (block808).

Exemplary Remote Server

In one aspect, a computer server (or smart infrastructure) configured touse telematics data associated with a first driver to facilitate safervehicle travel for a second driver may be provided. The computer servermay include (1) a communication unit configured to receive telematicsdata via wireless communication and/or data transmission, the telematicsdata being generated and transmitted from a first mobile device and/orfirst smart vehicle associated with a first driver, (2) a memory unitconfigured to store vehicle navigation information, virtual road maps,and/or computer-readable instructions; and (3) a processor configured toaccess the memory unit and to automatically identify or determine: (i) atravel or traffic event associated with the first mobile device and/orfirst vehicle, (ii) a Global Positioning System (GPS) location or otherlocation of the travel event, and (iii) an estimated or actualgeographical or temporal scope of the travel event from computeranalysis of the telematics data, the processor further being configuredto generate a travel event-related data transmission or wirelesscommunication associated with or detailing the travel event, or locationor extent thereof. The communication unit may be further configured totransmit the travel event-related data transmission or wirelesscommunication to a second mobile device or second vehicle associatedwith the second driver to facilitate the second mobile device or secondvehicle taking corrective action to enable safer vehicle travel for thesecond driver based upon the telematics data associated with the firstdriver.

The telematics data may include data that is indicative of a speed,acceleration, deceleration, location, and/or lane information associatedwith the first mobile device or the first vehicle. Additionally oralternatively, the telematics data may include data that is indicativeof a time, braking, acceleration, left turn, right turn, heading GPSspeed, GPS latitude and longitude, gyroscope, battery level, and/ortelephone usage information or data associated with, the first mobiledevice or the first vehicle. Thus, the travel event may be based upon ordetermined from, for example, the telematics data, which may revealvehicle conditions, traffic, congestion, road construction, and/orweather conditions, etc.

The preventive or corrective action taken by the second mobile device orsecond vehicle may include, for example, (i) generating or determiningan alert; (ii) presenting a visual alert on a display or display screenassociated with the second mobile device or the second vehicle; (iii)providing an audible alert; (iv) generating determining or receiving analternate travel route that avoids a GPS location of the travel event;(v) presenting the alternative travel route on a display or displayscreen for use by the driver; and/or (vi) automatically directing thesecond vehicle to autonomously take or follow the alternative travelroute.

Furthermore, the second mobile device or second vehicle may presentedthe alert only after the second mobile device or second vehicledetermines that the travel event is relevant to the second vehicle. Thisrelevance may be determined, for example, via a determination that alocation of the travel event is in the vicinity or within apredetermined distance of the second vehicle and along a route that thesecond vehicle is presently traveling.

Additionally or alternatively, the processor may be further configuredto listen for a telematics data-related wireless communication or datatransmission, and to store associated telematics data received via thecommunication unit in the memory unit when the telematics data-relatedwireless communication or data transmission is detected or within range.In addition, the communication unit may be further configured to relayor otherwise re-transmit the telematics data or the telematicsdata-related wireless communication or data transmission to otherlistening devices, including other vehicles, mobile devices, and/orsmart infrastructure, for example.

The computer server and/or smart infrastructure may include additional,fewer, and/or alternate components (and functionality), including thosediscussed elsewhere herein.

Exemplary Smart Road-Side Infrastructure

In another aspect, a smart infrastructure component configured to usetelematics data from a first driver to facilitate safer vehicle travelfor a second driver may be provided. The smart infrastructure componentmay include (1) a communication unit configured to receive a datatransmission or wireless communication containing or includingtelematics data, the telematics data being generated and transmittedfrom a first mobile device or a first vehicle associated with the firstdriver; (2) a memory unit configured to store vehicle navigationinformation, virtual road maps, and computer-readable instructions; and(3) a processor configured to access the memory unit to automaticallyidentify or determine: (i) a travel event; (ii) a Global PositioningSystem (GPS) location or other location of the travel event; and (iii)an estimated or actual geographical or temporal scope of the travelevent from computer analysis of the telematics data, the processorfurther being configured to generate a travel event-related datatransmission or wireless communication associated with or detailing thetravel event, or location or extent thereof. The communication unit maybe further configured to transmit the travel event-related datatransmission or wireless communication to a second mobile device and/orsecond vehicle associated with the second driver to facilitate thesecond mobile device or second vehicle taking corrective action toenable safer vehicle travel for the second driver based upon thetelematics data associated with the first driver.

Again, the telematics data may include data that is indicative of aspeed, acceleration, deceleration, location, and/or lane informationassociated with the first mobile device or the first vehicle.Additionally or alternatively, the telematics data may include data thatis indicative of a time, braking, acceleration, left turn, right turn,heading, GPS speed, GPS latitude and longitude, gyroscope, batterylevel, and/or telephone usage information or data associated with, thefirst mobile device or the first vehicle. Thus, the travel event may bebased upon or determined from, for example, the telematics data, whichmay reveal vehicle conditions, traffic, congestion, road construction,and/or weather conditions, etc.

Furthermore, as discussed above and elsewhere herein, the preventive orcorrective action taken by the second mobile device or second vehiclemay include, for example, (i) generating or determining an alert; (ii)presenting a visual alert on a display or display screen associated withthe second mobile device or the second vehicle; (iii) providing anaudible alert; (iv) generating determining or receiving an alternatetravel route that avoids a GPS location of the travel event; (v)presenting the alternative travel route on a display or display screenfor use by the driver; and/or (vi) automatically directing the secondvehicle to autonomously take or follow the alternative travel route.

The second mobile device or second vehicle may presented the alert onlyafter the second mobile device or second vehicle determines that thetravel event is relevant to the second vehicle. This relevance may bedetermined, for example, via a determination that a location of thetravel event is in the vicinity or within a predetermined distance ofthe second vehicle and along a route that the second vehicle ispresently traveling.

Additionally or alternatively, the processor may be further configuredto listen for a telematics data-related wireless communication or datatransmission, and to store associated telematics data received via thecommunication unit in the memory unit when the telematics data-relatedwireless communication or data transmission is detected or within range.In addition, the communication unit may be further configured to relayor otherwise re-transmit the telematics data or the telematicsdata-related wireless communication or data transmission to otherlistening devices, including other vehicles, mobile devices, and/orsmart infrastructure, for example.

The smart infrastructure component may include additional, less, oralternate functionality, including that discussed elsewhere hereinand/or below.

Exemplary Intermediate Mobile Device/Smart Vehicle

In yet another aspect, an intermediate mobile device or smart vehicleconfigured to use telematics and/or other data from a first driver tofacilitate safer vehicle travel for a second driver, the intermediatemobile device or smart vehicle may be provided. The intermediate mobiledevice or smart vehicle may include (1) a communication unit configuredto receive a data transmission or wireless communication containing orincluding telematics data, the telematics data being generated andtransmitted from a first mobile device or first smart vehicle associatedwith the first driver; (2) a memory unit configured to store vehiclenavigation information, virtual road maps, and/or computer-readableinstructions; (3) a processor configured to access the memory unit toautomatically identify or determine: (i) a travel event; (ii) a GlobalPositioning System (GPS) location or other location of the travel event;and (iii) an estimated or actual geographical or temporal scope of thetravel event from computer analysis of the telematics data, theprocessor further being configured to generate a travel event-relateddata transmission or wireless communication associated with or detailingthe travel event, or location or extent thereof. The communication unitmay be further configured to transmit the travel event-related datatransmission or wireless communication to a second or destination mobiledevice and/or a second smart vehicle associated with the second drivervia peer-to-peer (P2P) communication to facilitate the second mobiledevice or second smart vehicle taking corrective action to enable safervehicle travel for the second driver based upon the telematics dataassociated with the first driver.

For instance, for the (a) remote server, (b) smart road-sideinfrastructure, and/or (c) intermediate mobile device or smart vehiclementioned above, the travel (or traffic) event may be based upon (and/ordetermined from telematics data that reveals) vehicle, traffic,congestion, road construction, and/or weather conditions. As discussedabove and elsewhere herein, the telematics data may include speed,acceleration, deceleration, location, lane information, and/or otherdata of or associated with, the first mobile device and/or first smartvehicle. The telematics data may include time, braking acceleration,left turn, right turn, heading GPS (Global Positioning System) speed,GPS latitude and longitude, gyroscope data, battery level, and/ortelephone usage information or data of or associated with, the firstmobile device and/or first vehicle.

The preventive or corrective action taken may be: generating ordetermining an alert, at or via the second mobile device and/or secondvehicle (or second smart vehicle controller); presenting a visual alert,at or via the second mobile device and/or second vehicle (or secondsmart vehicle controller), on a display or display screen associatedwith the mobile device (and/or smart vehicle controller); and/orproviding an audible alert, at or via the second mobile device and/orsecond vehicle. The alert may be presented only after the second mobiledevice (or second vehicle or vehicle controller) determines that thetravel event is relevant to the second vehicle, such as by determiningthat a location of the travel event is in the vicinity of the secondvehicle and/or along a route that the second vehicle is presentlytraveling.

The preventive or corrective action taken may be: generating determiningand/or receiving an alternate travel route that avoids a GPS location ofthe travel (or traffic) event, at or via the second mobile device and/orsecond vehicle (or vehicle controller); and/or presenting thealternative travel route, at or via the second mobile device and/orsecond vehicle (or vehicle controller), on a display or display screenfor use by the driver. Additionally or alternatively, the preventive orcorrective action taken may be: generating determining and/or receivingan alternate travel route that avoids a GPS location of the travel (ortraffic) event, at or via the second mobile device and/or second vehicle(or vehicle controller); and/or automatically directing the secondvehicle to take or follow the alternative travel route, at or via thesecond mobile device and/or second vehicle (or vehicle controller), suchas by directing an autonomous vehicle to take the alternate travelroute.

The (a) remote server, (b) smart infrastructure component, and/or (c)intermediate mobile device or smart vehicle may be configured to: listenfor a telematics data-related wireless communication and/or datatransmission, and when the telematics data-related wirelesscommunication and/or data transmission is detected and/or within range,then (i) receive the telematics data-related wireless communicationand/or data transmission; (ii) store associated telematics data in amemory unit; and/or (iii) relay or otherwise re-transmit the telematicsdata and/or the telematics data-related wireless communication and/ordata transmission to other listening devices, such as other vehicles,mobile device, remote servers, and/or smart infrastructure, for example.

The intermediate mobile device or smart vehicle may include additional,less, or alternate functionality, including that discussed elsewhereherein.

Insurance Applications

As noted herein, the present embodiments may be used to adjust, update,and/or generate insurance policies. Insurance policies, such as auto,usage-based, home, and/or household insurance policies, may be adjusted,updated, and/or generated for insureds or potential customers that havemobile devices and/or vehicles that are equipped or configured with oneor more of the functionalities discussed herein.

For instance, insureds or family members may have mobile devices and/orvehicle that are configured to receive telematics data associated withother vehicles and/or abnormal road or travel conditions that otherdrivers are experiencing. The telematics may be received directly fromother vehicles, or indirectly from smart infrastructure and/or insuranceprovider remote servers. As a result, the insureds and/or their familymembers may be timely notified of traffic or travel events and then maytake alternate routes (or even not drive or delay driving) to lowertheir risk of getting in an accident due to the traffic or travelevents. An insurance provider may promote or reward such risk-aversebehavior and/or safer driving with lower insurance premiums, rates,and/or increased discounts, such as for usage-based or other types ofauto insurance.

Furthermore, an insurance provider may promote or reward the use of oneor more aspects described herein with lower insurance premiums, rates,and/or increased discounts. For example, an insurer may providediscounts or other incentives upon an insured customer installing anapplication to their mobile computing device that enables the mobilecomputing device to broadcast telematics data and/or to generate alertnotifications based upon telematics data received from other devices.

Additionally or alternatively, an insurer may provide discounts or otherincentives upon an amount that an insured customer uses the telematicsapplication on their mobile computing device that enables the mobilecomputing device to broadcast telematics data and/or to generate alertnotifications based upon telematics data received from other devices.Such usage-based discounts or incentives may be based upon amount oftime of or number of miles of, use or usage, e.g., an amount of time ormiles that the insured drove during a specific period with a TelematicsApp running or executing on their mobile device (which was locatedwithin the insured vehicle as it travels), the Telematics App configuredto collect and broadcast telematics data, and/or to receive telematicsdata from other vehicles or devices, and generate alerts orrecommendations based upon the data received.

Additional Considerations

With the foregoing, an insurance customer may opt-in to a reward,insurance discount, or other type of program. After the insurancecustomer provides their affirmative consent, an insurance providertelematics application and/or remote server may collect telematicsand/or other data (including image or audio data) associated withinsured assets, including before, during and/or after aninsurance-related event or vehicle collision. In return, risk-aversedrivers, and/or vehicle owners may receive discounts or insurance costsavings related to auto, home, life, and other types of insurance fromthe insurance provider.

In one aspect, telematics data, and/or other data, including the typesof data discussed elsewhere herein, may be collected or received by aninsured's mobile device or smart vehicle, a Telematics App (includingthose discussed herein), and/or an insurance provider remote server,such as via direct or indirect wireless communication or datatransmission from a Telematics App running on the insured's mobiledevice, after the insured or customer affirmatively consents orotherwise opts-in to an insurance discount, reward, or other program.The insurance provider may then analyze the data received with thecustomer's permission to provide benefits to the customer. As a result,risk-averse customers may receive insurance discounts or other insurancecost savings based upon data that reflects low risk driving behaviorand/or technology that mitigates or prevents risk to (i) insured assets,such as vehicles or even homes, and/or (ii) vehicle operators orpassengers.

Although the disclosure provides several examples in terms of twovehicles, two mobile computing devices, two on-board computers, etc.,aspects include any suitable number of mobile computing devices,vehicles, etc. For example, aspects include an external computing devicereceiving telematics data and/or geographic location data from a largenumber of mobile computing devices (e.g., 100 or more), and issuingalerts to those mobile computing devices in which the alerts arerelevant in accordance with the various techniques described herein.

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the description is defined by the words of the claims set forthat the end of this patent and equivalents. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment since describing every possible embodiment would beimpractical. Numerous alternative embodiments may be implemented, usingeither current technology or technology developed after the filing dateof this patent, which would still fall within the scope of the claims.

The following additional considerations apply to the foregoingdiscussion. Throughout this specification, plural instances mayimplement components, operations, or structures described as a singleinstance. Although individual operations of one or more methods areillustrated and described as separate operations, one or more of theindividual operations may be performed concurrently, and nothingrequires that the operations be performed in the order illustrated.Structures and functionality presented as separate components in exampleconfigurations may be implemented as a combined structure or component.Similarly, structures and functionality presented as a single componentmay be implemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (e.g., code embodiedon a machine-readable medium or in a transmission signal) or hardware.In hardware, the routines, etc., are tangible units capable ofperforming certain operations and may be configured or arranged in acertain manner. In example embodiments, one or more computer systems(e.g., a standalone, client or server computer system) or one or morehardware modules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules may provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and may operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing” “calculating,” “determining,”“presenting,” “displaying” or the like may refer to actions or processesof a machine (e.g., a computer) that manipulates or transforms datarepresented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof are intendedto cover a non-exclusive inclusion. For example, a process, method,article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription, and the claims that follow, should be read to include oneor at least one and the singular also includes the plural unless it isobvious that it is meant otherwise.

The patent claims at the end of this patent application are not intendedto be construed under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being explicitly recited in the claim(s).

This detailed description is to be construed as exemplary only and doesnot describe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One may be implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

What is claimed:
 1. A remote server configured to use telematics dataassociated with a first vehicle to facilitate safer vehicle travel for asecond vehicle, the remote server comprising: a communication unitconfigured to receive telematics data that is sampled by one or moresensors that are incorporated as part of a first computing device; and aprocessor configured to (i) identify a travel event, and (ii) generate atravel event-related data transmission indicative of informationassociated with the travel event based upon an analysis of thetelematics data, wherein the communication unit is further configured totransmit the travel event-related data transmission to a secondcomputing device or the second vehicle, which is associated with asecond driver, when the travel event is relevant to the second computingdevice or the second vehicle, to thereby cause at least one of thesecond computing device or the second vehicle to (1) at least one of:(i) provide, via the second computing device, a graphical user interface(GUI) including a display of: (a) an indication of a description of thetravel event, the indication of the description of the travel eventincluding at least one of a text indication of the description or agraphical indication of the description, and (b) an indication of alocation of the travel event, the indication of the location of thetravel event including at least one of a text indication of thelocation, a graphical indication of the location, or a map indicatingthe location, or (ii) direct at least one other corrective action thataffects driving of the second vehicle, and (2) display insurance policypricing adjustment information associated with the second vehicle thatis based upon a driver risk due to the identified travel event, so as topromote or reward risk averse behavior and safer driving.
 2. The remoteserver of claim 1, wherein the processor is further configured todetermine that the travel event is relevant to the second computingdevice or the second vehicle associated with the second driver when thetravel event is located on a same road as that of the second computingdevice or the second vehicle.
 3. The remote server of claim 1, whereinthe telematics data indicates that the first vehicle is experiencing oneor more of high traffic conditions, congestion, road construction, andextreme weather conditions.
 4. The remote server of claim 1, wherein thetelematics data is indicative of one or more of Global PositioningSystem (GPS) speed, GPS location, lane information associated with thefirst vehicle, time, turning associated with the first vehicle, GPSlatitude and longitude, battery level associated with the first vehicle,and telephone usage information associated the first vehicle.
 5. Theremote server of claim 1, wherein the communication unit is furtherconfigured to relay the telematics data to smart infrastructure.
 6. Theremote server of claim 1, wherein the communication unit is configuredto transmit the travel event-related data transmission to the secondcomputing device or the second vehicle to thereby cause the at least oneof the second computing device or the second vehicle to (i) generate analternate travel route that avoids the location of the travel event, and(ii) present the alternate travel route via the GUI.
 7. The remoteserver of claim 1, wherein the second vehicle is an autonomous vehicle,and wherein the communication unit is configured to transmit the travelevent-related data transmission to the second computing device or thesecond vehicle to thereby cause the second vehicle to autonomouslyfollow an alternate travel route that avoids the location of the travelevent.
 8. A smart infrastructure component configured to use telematicsdata from a first vehicle to facilitate safer travel for a secondvehicle, the smart infrastructure component comprising: a communicationunit configured to receive telematics data that is sampled by one ormore sensors that are incorporated as part of a first computing device;and a processor configured to (i) identify a travel event, and (ii)generate a travel event-related data transmission indicative ofinformation associated with the travel event based upon an analysis ofthe telematics data, wherein the communication unit is furtherconfigured to transmit the travel event-related data transmission to asecond computing device or the second vehicle, which is associated witha second driver, when the travel event is relevant to the secondcomputing device or the second vehicle, to thereby cause at least one ofthe second computing device or the second vehicle to (1) at least oneof: (i) provide, via the second computing device, a graphical userinterface (GUI) including a display of: (a) an indication of adescription of the travel event, the indication of the description ofthe travel event including at least one of a text indication of thedescription or a graphical indication of the description, and (b) anindication of a location of the travel event, the indication of thelocation of the travel event including at least one of a text indicationof the location, a graphical indication of the location, or a mapindicating the location, or (ii) direct at least one other correctiveaction that affects driving of the second vehicle, and (2) displayinsurance policy pricing adjustment information associated with thesecond vehicle that is based upon a driver risk due to the identifiedtravel event, so as to promote or reward risk averse behavior and saferdriving.
 9. The smart infrastructure component of claim 8, wherein theprocessor is further configured to determine that the travel event isrelevant to the second computing device or the second vehicle associatedwith the second driver when the travel event is located on a same roadas that of the second computing device or the second vehicle.
 10. Thesmart infrastructure component of claim 8, wherein the telematics dataindicates that the first vehicle is experiencing one or more of hightraffic conditions, congestion, road construction, and extreme weatherconditions.
 11. The smart infrastructure component of claim 8, whereinthe telematics data is indicative of one or more of Global PositioningSystem (GPS) speed, GPS location, lane information associated with thefirst vehicle, time, turning associated with the first vehicle, GPSlatitude and longitude, battery level associated with the first vehicle,and telephone usage information associated the first vehicle.
 12. Thesmart infrastructure component of claim 8, wherein the communicationunit is further configured to receive the telematics data relayed from aremote server, the remote server initially receiving the telematicsdata.
 13. The smart infrastructure component of claim 8, wherein thecommunication unit is configured to transmit the travel event-relateddata transmission to the second computing device or the second vehicleto thereby cause the at least one of the second computing device or thesecond vehicle to (i) generate an alternate travel route that avoids thelocation of the travel event, and (ii) present the alternate travelroute via the GUI.
 14. The smart infrastructure component of claim 8,wherein the second vehicle is an autonomous vehicle, and wherein thecommunication unit is configured to transmit the travel event-relateddata transmission to the second computing device or the second vehicleto thereby cause the second vehicle to autonomously follow an alternatetravel route that avoids the location of the travel event.
 15. Anintermediate mobile computing device configured to use telematics datafrom a first vehicle to facilitate safer vehicle travel for a secondvehicle, the intermediate mobile device comprising: a communication unitconfigured to receive telematics data that is sampled by one or moresensors that are incorporated as part of a first computing device; and aprocessor configured to (i) identify a travel event, and (ii) generate atravel event-related data transmission indicative of informationassociated with the travel event based upon an analysis of thetelematics data, wherein the communication unit is further configured totransmit the travel event-related data transmission to a secondcomputing device or the second vehicle, which is associated with asecond driver, when the travel event is relevant to the second computingdevice or the second vehicle, to thereby cause at least one of thesecond computing device or the second vehicle to (1) at least one of:(i) provide, via the second computing device, a graphical user interface(GUI) including a display of: (a) an indication of a description of thetravel event, the indication of the description of the travel eventincluding at least one of a text indication of the description or agraphical indication of the description, and (b) an indication of alocation of the travel event, the indication of the location of thetravel event including at least one of a text indication of thelocation, a graphical indication of the location, or a map indicatingthe location, or (ii) direct at least one other preventive or correctiveaction that affects driving of the second vehicle, and (2) displayinsurance policy pricing adjustment information associated with thesecond vehicle that is based upon a driver risk due to the identifiedtravel event, so as to promote or reward risk averse behavior and saferdriving.
 16. The intermediate mobile computing device of claim 15,wherein the processor is further configured to determine that the travelevent is relevant to the second computing device or the second vehicleassociated with the second driver when the travel event is located on asame road as that of the second computing device or the second vehicle.17. The intermediate mobile computing device of claim 15, wherein thetelematics data indicates that the first vehicle is experiencing one ormore of high traffic conditions, congestion, road construction, andextreme weather conditions.
 18. The intermediate mobile computing deviceof claim 15, wherein the telematics data is indicative of one or more ofGlobal Positioning System (GPS) speed, GPS location, lane informationassociated with the first vehicle, time, turning associated with thefirst vehicle, GPS latitude and longitude, battery level associated withthe first vehicle, and telephone usage information associated the firstvehicle.
 19. The intermediate mobile computing device of claim 15,wherein the communication unit is configured to transmit the travelevent-related data transmission to the second computing device or thesecond vehicle to thereby cause the at least one of the second computingdevice or the second vehicle to (i) generate an alternate travel routethat avoids the location of the travel event, and (ii) present thealternate travel route via the GUI.
 20. The intermediate mobilecomputing device of claim 15, wherein the second vehicle is anautonomous vehicle, and wherein the communication unit is configured totransmit the travel event-related data transmission to the secondcomputing device or the second vehicle to thereby cause the secondvehicle to autonomously follow an alternate travel route that avoids thelocation of the travel event.